Hi,
Am 05.09.2011 14:45, schrieb Hugo Mills:
It'd be good if you have the time to try to reproduce this,
particularly with the latest kernels (3.0 or 3.1-rcX)
My recovery is done. Here are some infos...
-
Linux-3.0.0-gentoo-x86_64-Intel-R-_Core-TM-_i7_CPU_965_@_3.20GHz-with-gentoo-2.0.3
-
Hi,
i've got an interesting btrfs subvolume problem which i can't
understand... Maybe someone here can give me a tip because i think
that's only a user error...
I had a root btrfs on / and made a subvolume some month ago for my home
on /home (i think cwd was / and i used btrfs subvolume create
Hi!
Thank you Hugo for your answers, but i have an update.
It's dead Jim.
When i tried to mount subvolid=0 to a temporary folder i got a kernel
segfault and a BUG line in btrfs kernel code somewhere (reproducable),
after a reboot all volumes are broken, can't be mounted anymore...
btrfsfsck
Did you manage to capture that output at all? (A photo would do).
Not yet, i am still on recovery from backup, that may take some time. If
i am done, i'll re-attach the broken btrfs system and dump some information.
It shouldn't be a big problem to redirect the kernel messages to a file.
Hi Ilya,
Am 05.09.2011 15:07, schrieb Ilya Dryomov:
Well, it's *sort of* expected if you think about it. When you mounted
after set-default, your /home is no longer a valid subvolume access
point (it was in the default subvolume, until you rebooted). Inside
your snapshot /home is just an
