Yan, Zheng yanzh...@21cn.com writes:
You can try mounting the FS in read only mode and copying files out.
If you still get that error, try making verify_parent_transid() in disk-io.c
always return 0. These are all we can do now.
Tried mounting it in read only mode, same problem:
- Unless I'm missing something, there doesn't seem to be any way later
on to see that I set the data policy to raid1, except using
btrfs-dump-tree and checking the flags bits for the appropriate
group. Which can make things confusing if I have a bunch of btrfs
Yeah df is just a fun ball of wax in many respects. We don't take into
account
RAID and we don't subtrace space thats strictly for metadata, so there are
several things that need to be fixed for df. Thanks,
But as we have said many times... if we have different
raid types
Hi,
the following testcase, if I remember the afternoon correctly, caused an
oops on 2.6.31.6:
some.vol; # aka truncate -s 0
truncate -s $[10*1048576*1024] some.vol;
mkfs.btrfs some.vol;
mount some.vol /some.where -oloop;
truncate -s $[30*1048576*1024] some.vol;
btrfsctl -r 30G /some.where;
Hi,
This left me puzzled for a while:
22:29 borg:/ # losetup /dev/loop1 /.B.disk
22:29 borg:/ # mount /dev/loop1 /B
mount: /dev/loop1: can't read superblock
22:29 borg:/ # blkid /dev/loop1
/dev/loop1: UUID=e19fe89b-cde3-4ccc-bc70-b759a57bd1c9
UUID_SUB=f29c6218-d040-4546-a227-4dd2d2142817
On Wed, Nov 18, 2009 at 10:31:53PM +0100, Jan Engelhardt wrote:
This left me puzzled for a while:
22:29 borg:/ # losetup /dev/loop1 /.B.disk
22:29 borg:/ # mount /dev/loop1 /B
mount: /dev/loop1: can't read superblock
22:29 borg:/ # blkid /dev/loop1
/dev/loop1:
I'm really not to sure who to report this too, but my btrfs / partiton
segfaults when mounting. It also segfaults when trying to run btrfsck.
My setup:
Gentoo x64 install in Virtualbox (Windows 7 x64 host). 2.6.32_rc6
kernel. Recently converted from an ext4 filesystem with the
btrfs-convert
