FWIW, for those following along: took the system down for a reboot last
night at 9PM EST, then tried the full send after the reboot - took 12
hours or so to complete, but completed no issues, as have a few
incremental sends since.
So, yeah, definitely looks related to kernel memory fragmentati
On Mon, Jan 13, 2014 at 02:03:52PM -0500, Jim Salter wrote:
> OK, thanks. If kernel memory fragmentation is a big factor, that would also
> explain why it succeeds after a reboot but does not succeed after weeks of
> uptime...
Yes, that's it.
--
To unsubscribe from this list: send the line "unsubs
OK, thanks. If kernel memory fragmentation is a big factor, that would
also explain why it succeeds after a reboot but does not succeed after
weeks of uptime...
On 01/13/2014 01:56 PM, David Sterba wrote:
On Mon, Jan 13, 2014 at 01:37:31PM -0500, Jim Salter wrote:
What makes you believe that?
On Mon, Jan 13, 2014 at 01:37:31PM -0500, Jim Salter wrote:
> What makes you believe that? The bug filed there appears to be related to
> defragging, which I am not doing either manually or automatically.
The quota groups are on and the symptoms match the known problem when
there are lots of backr
What makes you believe that? The bug filed there appears to be related
to defragging, which I am not doing either manually or automatically.
On 01/13/2014 01:23 PM, David Sterba wrote:
On Mon, Jan 13, 2014 at 07:58:48AM -0500, Jim Salter wrote:
Getting sporadic page allocation failures in btrf
On 01/13/2014 01:23 PM, David Sterba wrote:
On Mon, Jan 13, 2014 at 07:58:48AM -0500, Jim Salter wrote:
Getting sporadic page allocation failures in btrfs send. This happened once
several weeks ago but was fine after a reboot; yesterday I did not reboot,
but had the failure back-to-back trying
On Mon, Jan 13, 2014 at 07:58:48AM -0500, Jim Salter wrote:
> Getting sporadic page allocation failures in btrfs send. This happened once
> several weeks ago but was fine after a reboot; yesterday I did not reboot,
> but had the failure back-to-back trying to send two different snapshots.
> These a
BTW, this problem occurred with the 3.11 kernel shipping by default in
Ubuntu Saucy as well as this 3.13rc7 daily kernel I'm using currently.
On 01/13/2014 10:44 AM, Wang Shilong wrote:
> Just double check, what is your kernel version to trigger this problem…
> I suppose this should be an older ke
> It's a pretty new kernel - 3.13.0-031300rc7-generic.
>
> Sorry if I'm misunderstanding something, but... how can I send with -p
> if the parent snapshot doesn't already exist on the target?
Obviously, you can not…
Sorry, i was just thinking you use all the operations in one machine just like
It's a pretty new kernel - 3.13.0-031300rc7-generic.
Sorry if I'm misunderstanding something, but... how can I send with -p
if the parent snapshot doesn't already exist on the target?
What I'm doing is btrfs send /.snapshots/name-of-snapshot | ssh
othermachine btrfs receive /.snapshots. If the pa
Just double check, what is your kernel version to trigger this problem…
I suppose this should be an older kernel? If yes, can you have a try at the
latest
upstream kernel and see if problem still exist?
Thanks,
Wang
>
> 在 2014-1-13，下午11:20，Jim Salter 写道：
>
>> Er... I can't use incremental s
在 2014-1-13，下午11:20，Jim Salter 写道：
> Er... I can't use incremental send if I can't get one full send to go through
> first. =)
sory, i mean one approach is use '-p' option, you can use:
# btrfs sub create subv
# btrfs sub snapshot -r subv snap
# btrfs sub snapshot -r sub snap1
# btrfs send
Er... I can't use incremental send if I can't get one full send to go
through first. =)
I'm hoping the problem will go away for long enough to get a full send
completed once I reboot the box, but I can't do that until (much) later
in the day.
On 01/13/2014 10:17 AM, Wang Shilong wrote:
Hell
Hello,
I took a careful think about your problems below, i think this is because btrfs
*ulist* implement use
krealloc which might cause memory allocation fails especial you use full send.
Before we kicked off now stupid *ulist* implements, i think you can use
incremental send to solve
this iss
Hi list -
Getting sporadic page allocation failures in btrfs send. This happened
once several weeks ago but was fine after a reboot; yesterday I did not
reboot, but had the failure back-to-back trying to send two different
snapshots. These are full sends, not incremental, of a bit over 600G of
15 matches
Mail list logo
