From: Harry <harry@pythonanywhere.com>
To: xfs@oss.sgi.com
Subject: trying to avoid a lengthy quotacheck by deleting all quota data
Date: Tue, 24 Feb 2015 15:15:26 +0000 [thread overview]
Message-ID: <54EC958E.2000001@pythonanywhere.com> (raw)
Hi there,
We've got a moderately large disk (~2TB) into an inconsistent state,
such that it's going to want a quotacheck the next time we mount it
(it's currently mounted with quota accounting inactive). Our tests
suggest this is going to take several hours, and cause an outage we
can't afford.
We're wondering whether there's a 'nuke the site from orbit' option that
will let us avoid it. The plan would be to:
- switch off quotas and delete them completely, using the commands:
-- disable
-- off
-- remove
- remount the drive with -o prjquota, hoping that there will not be a
quotacheck, because we've deleted all the old quota data
- run a script gradually restore all the quotas, one by one and in good
time, from our own external backups (we've got the quotas in a database
basically).
So the questions are:
- is there a way to remove all quota information from a mounted drive?
(the current mount status seems to be that it tried to mount it with -o
prjquota but that quota accounting is *not* active)
- will it work and let us remount the drive with -o prjquota without
causing a quotacheck?
Answers on a postcard, received with the utmost gratitude.
Rgds,
Harry + the PythonAnywhere team.
--
Harry Percival
Developer
harry@pythonanywhere.com
PythonAnywhere - a fully browser-based Python development and hosting environment
<http://www.pythonanywhere.com/>
PythonAnywhere LLP
17a Clerkenwell Road, London EC1M 5RD, UK
VAT No.: GB 893 5643 79
Registered in England and Wales as company number OC378414.
Registered address: 28 Ely Place, 3rd Floor, London EC1N 6TD, UK
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2015-02-24 15:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 15:15 Harry [this message]
2015-02-24 16:39 ` trying to avoid a lengthy quotacheck by deleting all quota data Harry
2015-02-24 17:33 ` Ben Myers
2015-02-24 17:59 ` Harry Percival
2015-02-24 18:12 ` Ben Myers
2015-02-24 21:59 ` Dave Chinner
2015-02-26 13:07 ` Harry
2015-03-05 13:15 ` Harry
2015-03-05 15:53 ` Eric Sandeen
2015-03-05 17:05 ` Harry
2015-03-05 17:09 ` Harry
2015-03-05 17:27 ` Eric Sandeen
2015-03-05 17:34 ` Harry
2015-03-05 17:44 ` Eric Sandeen
2015-03-05 18:07 ` Harry
2015-03-05 20:08 ` Eric Sandeen
2015-03-06 11:27 ` Harry Percival
2015-03-06 21:11 ` Dave Chinner
2015-03-25 12:34 ` Harry Percival
2015-03-07 13:41 ` Arkadiusz Miśkiewicz
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=54EC958E.2000001@pythonanywhere.com \
--to=harry@pythonanywhere.com \
--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