From: Arjan van de Ven <arjan@infradead.org>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Jim Dennis <jimd@starshine.org>, linux-kernel@vger.kernel.org
Subject: Re: SEEK_HOLE and SEEK_DATA support?
Date: Fri, 03 Mar 2006 10:15:05 +0100 [thread overview]
Message-ID: <1141377306.2883.22.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <1141374797.3042.95.camel@mindpipe>
On Fri, 2006-03-03 at 03:33 -0500, Lee Revell wrote:
> On Thu, 2006-03-02 at 13:49 -0800, Jim Dennis wrote:
> >
> > I ask primarily because of the interplay between 64-bit systems and
> > things like /var/log/lastlog (which appears as a 1.2TiB file due to
> > the nfsnobody UID of 4294967294).
> >
> > (I'm realize that adding support for these additional seek() flags
> > wouldn't solve the problem ... archiving tools would still have to
> > implement it. And I can also hear the argument that Red Hat and other
> > distributions should re-implement lastlog handling to use a more modern
> > and efficient hashing/index format and perhaps that they should set
> > nfsnobody to "-1" ...
>
> So the presence of very high UIDs causes lastlog to be huge? That just
> sounds like a RedHat bug.
it causes it to be a sparse file
lastlog is an array based file format ;)
but sparse
next prev parent reply other threads:[~2006-03-03 9:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 21:49 Jim Dennis
2006-03-03 8:33 ` Lee Revell
2006-03-03 9:15 ` Arjan van de Ven [this message]
2006-03-05 3:05 ` Andrew Morton
2006-03-05 4:18 ` Nicholas Miell
2006-03-03 17:04 Jim Dennis
2006-03-03 17:56 ` Phillip Susi
2006-03-03 22:03 ` Nicholas Miell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1141377306.2883.22.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=jimd@starshine.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®