On 05/08/2011 09:36 AM, Daniel J Blueman wrote:

On 12 April 2011 00:07, Daniel J Blueman[off-list ref]  wrote:

quoted

On 11 April 2011 23:32, Josef Bacik[off-list ref]  wrote:

quoted

On 04/10/2011 04:29 AM, Daniel J Blueman wrote:

quoted

When rebooting from a crash, thus during log replay on 2.6.29-rc2,
btrfs_insert_dir_item caused an assertion failure [1]. The fs was
being mounted clear_cache on an SSD.

Probably it's not so easy to reproduce, but better to report it...

Do you still have this fs, and does it still panic the same way on mount?
  Thanks,

I still have this fs, though it didn't panic at next mount. I guess
this creates a case for cooking a script that eg logically disconnects
a block device during activity (hdparm or echo 1>delete) then
reconnects it for remount...let me know if interested.

I've hit this a few times recently following a crash in 2.6.39-rc (eg
with -rc6 [1]) and have found the only way to access the data is mount
-o ro,notreelog.

I guess btrfs_insert_dir_item is failing due to corruption of the
directory inode. The only solution here would be to gracefully discard
the log item being replayed and print a warning that the filesystem
has corruption, right?

Well this is -ENOSPC, so we need to figure out why we're getting ENOSPC 
and fix that, or if it's valid we need to just fail to mount and let the 
user decide if they want to discard the tree log.  Thanks,

Josef