re-install and formatting with btrfs - including md5
checksumming and had no defects before and did not see any block-level
errors before the oops.
regards
Roland
[ 3246.471638] [ cut here ]
[ 3246.471729] kernel BUG at
/build/buildd-linux-2.6_3.1.1-1-i386-6vi5gY/linux
- 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
if it's possible to come up with a way to make things
consistent at least, or figure out a way to define more useful
information about space left on the filesystem.
- Roland
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord
in general what we should say for a
metadata-only mirrored filesystem, since we don't really know in
advance how much space we have exactly)
I'm happy to help fix these issues up; just want to make sure I'm not
missing something or doing it wrong.
Thanks,
Roland
--
To unsubscribe from this list
when this
feature will be available ?
i wonder if it`s just so hard to implement or if it`s just too low priority
on the todo list. maybe both ? ;)
regards
roland
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
I don't disagree, please do keep in mind that I'm not suggesting anyone
use this in production yet.
When it's in mainline I suspect people will start using it for that.
I think the larger question here is where we want development to happen.
I'm definitely not pretending that
i have some difficulty in understanding multi-device handling in depth.
as
http://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices
tells,
btrfs can span over multiple devices at the same time. (great feature,
btw !)
ok then:
mkfs.btrfs -m single -d single /dev/sdb
as expected.
now, the weird thing is, that on /btrfs-mount this behaves different.
autocompletion for testdir works, but not for linux dir. weird.
can someone reproduce this ?
i`m on opensuse 11.1 with 2.6.27.8-1-default and latest btrfs-unstable from
git.
regards
roland
--
To unsubscribe
