| To: | Steve Lord <lord@xxxxxxx> |
|---|---|
| Subject: | Re: Locking bmap mappings |
| From: | "Andi Kleen" <ak@xxxxxxx> |
| Date: | Tue, 29 Aug 2000 00:36:59 +0200 |
| Cc: | "Andi Kleen" <ak@xxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <200008282123.QAA24574@jen.americas.sgi.com>; from lord@sgi.com on Mon, Aug 28, 2000 at 04:23:32PM -0500 |
| References: | <ak@suse.de> <200008282123.QAA24574@jen.americas.sgi.com> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
On Mon, Aug 28, 2000 at 04:23:32PM -0500, Steve Lord wrote: > > > > > Sorry, I should have been more clear. The locking is required for external > > users, e.g. the loop device (the current version doesn't do it, but it will > > be fixed to do so). loop device cannot access any internal XFS locks. > > > > > > -Andi > > OK, that's a different kettle of fish.... It would be nice if you could commit (or whatever ptools calls that) it. Thanks, -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | ADD 800297 - repair doesn't recover if primary sb is trashed, nathans@xxxxxxxxxxxx |
|---|---|
| Next by Date: | TAKE - write performance improvement, Ananth Ananthanarayanan |
| Previous by Thread: | Re: Locking bmap mappings, Steve Lord |
| Next by Thread: | Re: Locking bmap mappings, Steve Lord |
| Indexes: | [Date] [Thread] [Top] [All Lists] |