Subject: Re: lseek() extension for spare files
To: Matthew Mondor <>
From: Bill Studenmund <>
List: tech-kern
Date: 09/22/2006 10:10:28
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Sep 22, 2006 at 08:23:35AM -0400, Matthew Mondor wrote:
> On Thu, 21 Sep 2006 17:07:38 -0700
> Bill Studenmund <> wrote:
> > I expect that how you'd use it is something like (warning, pseudo-code,=
> > lots of stuff glossed over):
> [...]
> Interesting...  just out of curiosity, could this by any chance also
> potentially allow to implement the -P option of rm(1) in a way that may
> work on file systems such as LFS (for which -P currently makes no
> sense), if LFS supported the new lseek(2) extensions?  Or would writing
> a block at the start of a data position immediately after the seek still
> cause that block to always be appended?

No, writing is always appended, even overwriting. To make rm -P work, we=20
need to have the file system step in and immediately re-write the segments=
containing data for this file.

Take care,


Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.4.3 (NetBSD)