Hi,
I was trying to remove a 'missing' drive from a raid1 setup. It was
suggested on this list that I update to HEAD. I updated my kernel to
Ubuntu-lts-2.6.37-2.9, which appears to have the latest BTRFS code in it. I
then tried to remove my missing drive again:
r...@willvo:~# btrfs
In the file sync path, file's parent inode is logged if it is newer than the
last
commit. This patch checks also the last_trans field as well as generation.
As btrfs_log_inode updates the logged_trans field of parent dir's inode,
tree-log
lookup operations are suppressed upon unlink.
The
On Sat, Nov 06, 2010 at 08:03:05PM +0900, Itaru Kitayama wrote:
In the file sync path, file's parent inode is logged if it is newer than the
last
commit. This patch checks also the last_trans field as well as generation.
As btrfs_log_inode updates the logged_trans field of parent dir's
My apologies if I missed it, but this looks like the most recent
version of this patch ([PATCH] Btrfs-progs: add support for mixed
data+metadata block groups V3), and this version needs updating to
take into account that BTRFS_FEATURE_INCOMPAT_SPACE_CACHE is no longer
needed.
The kernel btrfs
After a successful db startup, this crash was reproducible every time with db
activity, or possibly just time. The filesystem is a raid1 and even after a
reformat and restore from backup, the crash remains:
Label: slash uuid: a9730db3-a475-45bb-af94-a873e235114b
Total devices 2 FS
