xfs
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: xfsdump stuck in io_schedule

from [Andi Kleen] [Permanent Link][Original]
To: Zlatko Calusic <zlatko.calusic@xxxxxxxx>
Subject: Re: xfsdump stuck in io_schedule
From: Andi Kleen <ak@xxxxxxx>
Date: Mon, 18 Nov 2002 00:14:25 +0100
Cc: Andrew Morton <akpm@xxxxxxxxx>, Stephen Lord <lord@xxxxxxx>, Andi Kleen <ak@xxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <dnzns7j507.fsf@xxxxxxxxxxxxxxxxx>
References: <20021115140635.A31836@xxxxxxxxxxxxx> <dnr8dmj1i1.fsf@xxxxxxxxxxxxxxxxx> <20021115164012.A28685@xxxxxxxxxxxxx> <87u1ih4x29.fsf@xxxxxxxxxxxxxx> <1037539697.1240.30.camel@xxxxxxxxxxxxxxxxxxxxxxx> <877kfcqmy5.fsf@xxxxxxxxxxxxxx> <3DD7EB2C.C20F312E@xxxxxxxxx> <87n0o8c7g5.fsf@xxxxxxxxxxxxxx> <3DD7F7CB.F292C9C7@xxxxxxxxx> <dnzns7j507.fsf@xxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.3.22.1i 
> I think I'll leave it to xfs guys now to fix it properly, I don't even
> understand why allocating pages for readahead needs to be atomic.

Probably because it should not block. readahead is optional.

-Andi
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: xfs_force_shutdown on rm, Chris Pascoe
Next by Date:  未承諾広告※電子メール広告, dmail5555jp
Previous by Thread:  Re: xfsdump stuck in io_schedule, Andrew Morton
Next by Thread:  Re: xfsdump stuck in io_schedule, Christoph Hellwig
Indexes:  [Date] [Thread] [Top] [All Lists]