On 05/08/2011 09:36 AM, Daniel J Blueman wrote:
On 12 April 2011 00:07, Daniel J Bluemandaniel.blue...@gmail.com wrote:
On 11 April 2011 23:32, Josef Bacikjo...@redhat.com wrote:
On 04/10/2011 04:29 AM, Daniel J Blueman wrote:
When rebooting from a crash, thus during log replay on
On 12 April 2011 00:07, Daniel J Blueman daniel.blue...@gmail.com wrote:
On 11 April 2011 23:32, Josef Bacik jo...@redhat.com wrote:
On 04/10/2011 04:29 AM, Daniel J Blueman wrote:
When rebooting from a crash, thus during log replay on 2.6.29-rc2,
btrfs_insert_dir_item caused an assertion
On 04/10/2011 04:29 AM, Daniel J Blueman wrote:
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
On 11 April 2011 23:32, Josef Bacik jo...@redhat.com wrote:
On 04/10/2011 04:29 AM, Daniel J Blueman wrote:
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
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...
--- [1]
kernel BUG at fs/btrfs/inode.c:4665!
invalid
