On 18/09/14 16:00, Chris Mason wrote:
Johannes and Sam, could you please confirm this patch fixes your mount
regression for now? Anand, please make sure I kept the generation check
properly.
I've just tested this patch on top of 3.17-rc5 and it fixes the issue
for me.
Thanks!
Sam
-
or /home busy
/dev/vda is already mounted on /
Sorry for the confusion here. I typed in the shell commands into the log
manually and obviously put /dev/sda when I meant /dev/vda.
I've retested with /dev/vda and the same error occurs.
On 15/09/2014 23:13, Sam Thursfield wrote
if (!fs_devices->opened)
device->generation = found_transid;
+out:
*fs_devices_ret = fs_devices;
return ret;
---
Anand
On 15/09/2014 23:54, Chris Mason wrote:
On 09/15/2014 11:13 AM, Sam Thursfield wro:
Hi!
I'm having an issue with the 3.17rc
of the comments in that commit.
Thanks
Sam
--
Sam Thursfield, Codethink Ltd.
Office telephone: +44 161 236 5575
$ btrfs subvolume list /
ID 257 gen 15 top level 5 path systems/factory/orig
ID 261 gen 15 top level 5 path state/var
ID 263 gen 11 top level 5 path state/opt
ID 264 gen 12 top level 5
[I'm resending this mail to list instead of as a personal reply, sorry]
On 09/03/2012 03:35 PM, cwillu wrote:
On Mon, Sep 3, 2012 at 8:23 AM, Sam Thursfield
wrote:
Hi
I've been running btrfs in various VMs for a while, and periodically I've
experienced corruption in the fi
Hi
I've been running btrfs in various VMs for a while, and periodically
I've experienced corruption in the filesystems being used. None of the
data is important, but I'd like to track down how the corruption
occurred in the first place.
Trying to mount any of the corrupt filesystems fails wi
