On Tue, 2009-05-05 at 12:51 -0700, Christian Kujau wrote: > On Tue, 5 May 2009, Chris Mason wrote: > > Somehow xen is turning a barrier request into an IO error. That's > > really quite strange, but you can mount -o nobarrier. > > Thanks for the quick reply - yes, that helped. So, is that something I > should report to the Xen folks? These "other filesystems" I can unmount > with no BUG :-)
For ext3, mount -o barrier=1 and you should see something exciting. It won't BUG because ext3 isn't as serious about telling the users about IO problems as we are, but you should at least see messages. > > > I just noted something else, but completely unrelated to that barrier > stuff: > > # ls -ld /mnt/d* > dr-xr-xr-x 1 root root 0 Jan 1 1970 /mnt/d1 > drwxr-xr-x 3 root root 4096 May 5 21:45 /mnt/d2 > # grep mnt/d /proc/mounts > /dev/xvdb /mnt/d1 btrfs rw,relatime,nobarrier 0 0 > /dev/xvdc /mnt/d2 ext3 rw,relatime,errors=continue,data=writeback 0 0 > > How comes btrfs thinks it has been created at the beginning of time? The mkfs.btrfs command needs to properly set the date on the root directory. Sorry, I never noticed that one. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
