On Sun, 2008-08-03 at 02:12 +0300, Ahmed Kamal wrote: > Hi guys, > I was playing on vmware with btrfs on complete disks /dev/sd{b,c,d,e}. > Next I decided to use partitions, so I created /dev/sd{b,c,d,e}1 and > used those, worked fine! Afterward, I mistakenly re-ran an old command > on the full disk ( mount -t btrfs -o subvol=. /dev/sdb /mnt/ ) notice > this is sdb not sdb1, and I got this spectacular kernel freeze. Let me > know if that's some bug.
It would be nice if we didn't oops, there is clearly some hardening to do in the failure paths for corrupt filesystems. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html