-It's not a brand new fs. It has been created four or five days ago with btrfs-progs 3.16.2 (in fact it was created because of the dead unremovable ro snapshots in the previous fs) -the snapshot in question has been created after applying the patch (and it has not become corrupted so far) -not an incremental send -no warnings in dmesg -btrfs check segfaults (as it did before the patch) -there are in fact dead unremovable ro snapshots in the filesystem (it has been used before the patch). But the filesystem seems functional as long as the dead ro snapshots aren't touched. If one of them is accessed with ls -l I get the usual "parent transid verify failed on X wanted Y found Z". But as I said no warnings of that kind (or any kind) appear in dmesg when I do the send on the freshly created ro snapshot. thanks john On Thu, Oct 16, 2014 at 1:05 AM, Filipe David Manana <fdmanana@xxxxxxxxx> wrote: > On Wed, Oct 15, 2014 at 11:42 PM, john terragon <jterragon@xxxxxxxxx> wrote: >> Hi. >> >> I applied the patch to 3.17.1 but although I haven't seen any >> corrupted ro snapshot yet it's still impossible to do btrfs send. As >> soon as I start btrfs send I still get >> >> ERROR: send ioctl failed with -12: Cannot allocate memory >> >> even if I redirect btrfs send's output to a file (instead of involving >> btrfs receive) >> >> Maybe this time it's actually a btrfs-progs bug? > > Not enough information to tell. > > Is it a brand new fs? If not, is it a snapshot created after applying > the patch or before? Does a btrfsck reports any issues with the fs? > Is it an incremental (using -p <parent_snapshot>) or a full send? Do > you see any warning (traces, errors) in syslog (dmesg)? > > Either an issue in send or, if it's an fs created/used with unpatched > 3.17.0/1, it can be a side effect of the corruption. > > thanks > >> >> Thanks >> John > > > > -- > Filipe David Manana, > > "Reasonable men adapt themselves to the world. > Unreasonable men adapt the world to themselves. > That's why all progress depends on unreasonable men." -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
