On Thu, Mar 20, 2014 at 12:13:36AM +0000, Chris Mason wrote:
> >Should I double it?
> >
> >For now, I have the copy running again, and it's been going for 8 hours
> >without failure on the old kernel but of course that doesn't mean my 2TB
> >copy will complete without hitting the bug again.
>
> Sorry, I misspoke, you should bump /proc/sys/vm/min_free_kbytes. Honestly
> though, it¹s just a bug in the mvs driver. Atomic 8K allocations are
> doomed to fail eventually.
Gotcha
polgara:/mnt/btrfs_backupcopy# cat /proc/sys/vm/min_free_kbytes
45056
polgara:/mnt/btrfs_backupcopy# echo 100000 > /proc/sys/vm/min_free_kbytes
polgara:/mnt/btrfs_backupcopy# cat /proc/sys/vm/min_free_kbytes
100000
polgara:/mnt/btrfs_backupcopy#
> The driver should either busy loop until the allocation completes (really
> not a great choice), gracefully deal with the failure (looks tricky), or
> preallocate the space (like the rest of the block layer).
Gotcha. I'll report this to the folks maintaining the marvel driver.
So just to make sure I got you right, although the page allocation failure
was shown in btrfs, it's really the underlying marvel driver at fault here,
and there isn't really anything to change on the btrfs side, correct?
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
--
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
