From: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: quotacheck speed
Date: Tue, 14 Feb 2012 06:35:45 +0100 [thread overview]
Message-ID: <201202140635.45902.arekm@maven.pl> (raw)
In-Reply-To: <20120213234235.GE14132@dastard>
On Tuesday 14 of February 2012, Dave Chinner wrote:
> On Mon, Feb 13, 2012 at 07:09:50PM +0100, Arkadiusz Miśkiewicz wrote:
> > On Monday 13 of February 2012, Christoph Hellwig wrote:
> > > On Sun, Feb 12, 2012 at 10:01:07PM +0100, Arkadiusz Mi??kiewicz wrote:
> > > > Hi,
> > > >
> > > > When mounting 800GB filesystem (after repair for example) here
> > > > quotacheck takes 10 minutes. Quite long time that adds to whole time
> > > > of filesystem downtime (repair + quotacheck).
> > > >
> > > > I wonder if quotacheck can be somehow improved or done differently
> > > > like doing it in parallel with normal fs usage (so there will be no
> > > > downtime) ?
> > >
> > > I think the best idea to improve the performance in case you did a
> > > repair is to integrate the quotacheck code into repair. It's fairly
> > > simple given that quotacheck simply walks all inodes and adds their
> > > space usage to the correct user/group/project, and given that repair
> > > already walks all inodes, and checks their block maps it does most of
> > > that work already.
> >
> > That would be interesting and probably make
> >
> > > The only downside would be that the memory usage
> > > of repair increases a bit by keeping the dquots in memoryb, but even
> > > for your 130000 dquot setup that would add about 100 bytes * 130000
> > > please a bit of in-memory metadata (less than 20MB total) of memory
> > > usage, so it probably is a good tradeoff.
> > >
> > >
> > > In what cases do you regularly run quotacheck when you did not do
> > > a repair first?
> >
> > I don't initiate quotacheck manually. AFAIK internal xfs quotacheck
> > happens in two cases here:
> > 1) repair->mount
> > 2) filesystem has quotacheck done properly some time ago -> umount ->
> > mount-
> >
> > >oops/reset/something like that happens while mounting -> new mount
>
> So you'd like both quotacheck to be sped up and repair
> to do it as well? ;)
Well, 1) is happening much more often than 2) :-)
--
Arkadiusz Miśkiewicz PLD/Linux Team
arekm / maven.pl http://ftp.pld-linux.org/
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-02-14 5:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-12 21:01 quotacheck speed Arkadiusz Miśkiewicz
2012-02-12 22:21 ` Dave Chinner
2012-02-13 18:16 ` Arkadiusz Miśkiewicz
2012-02-13 23:13 ` Dave Chinner
2012-02-12 23:44 ` Christoph Hellwig
2012-02-13 0:17 ` Peter Grandi
2012-02-13 18:09 ` Arkadiusz Miśkiewicz
2012-02-13 23:42 ` Dave Chinner
2012-02-14 5:35 ` Arkadiusz Miśkiewicz [this message]
2012-02-15 10:39 ` Arkadiusz Miśkiewicz
2012-02-15 21:45 ` Dave Chinner
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=201202140635.45902.arekm@maven.pl \
--to=arekm@maven.pl \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.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