On Tue, Sep 22, 2015 at 08:55:05AM -0300, Sylvain Joyeux wrote: > Hi > > Hopefully, third time's the charm ... this time I'm subscribed. > > (NB: sorry if you got this twice, but it did not appear in the ML > archives so I'm assuming it never reached the ML ...) > > I am in the situation where a partition has errors, detected by > btrfs-check but not repaired by it. Mounting the partition causes > always the same kernel errors to be reported on dmesg. > > I get these errors with a 4.2 kernel and btrfs-progs 4.2. The > partition has been used on a mixture of 4.0.7 and 4.2 kernels (I have > to reboot on 4.0 when I need to use the NVidia card), and I really am > unable to pinpoint whether it happened first on 4.0 or 4.2... > > I use this partition mostly as a target for btrfs send / btrfs receive > - type backups (synchronization of snapper-based snapshotting), and > really did nothing fancy beyond that (which, well, is in itself > fancy). So, no big deal for now for me, I just thought that a > non-repairable corrupted filesystems could be of interest. > > Attached: > - the output of btrfs check. btrfs check --repair does not fix them. > - the dmesg output with the kernel errors
Not attached to this email. :) Can you just put the text inline? It's more likely to be picked up by the mail archivers, and it's generally easier to view and comment on. Hugo. > I can provide the partition image as created by btrfs-image, but it's > 230MB in size, don't know where to put it > > Note: since it was a week or so ago, I reinitialized the partition, > and just got the exact same problem today. The only thing a bit out of > the ordinary about this partition is that it is mounted in two > different places, and that I have some VMs on it, and am using the > nocow attribute on the VM files. > > Regards, > Sylvain -- Hugo Mills | "Can I offer you anything? Tea? Seedcake? Glass of hugo@... carfax.org.uk | Amontillado?" http://carfax.org.uk/ | PGP: E2AB1DE4 | Mrs Gillyflower, Doctor Who
signature.asc
Description: Digital signature
