From: Harry Percival <harry@pythonanywhere.com>
Cc: xfs@oss.sgi.com
Subject: Re: trying to avoid a lengthy quotacheck by deleting all quota data
Date: Wed, 25 Mar 2015 12:34:00 +0000 [thread overview]
Message-ID: <5512AB38.7060009@pythonanywhere.com> (raw)
In-Reply-To: <20150306211136.GB13958@dastard>
We've written up a sort of post-mortem blog post describing the whole saga:
http://blog.pythonanywhere.com/110/
We've tried hard to avoid kicking off some kind of filesystem flamewar
while describing the whys and wherefores of our move from xfs to ext4,
but if you feel we've misrepresented anything, do let us know, I'm sure
we can adjust the post.
Thanks again to everyone for your help debugging this stuff, and for a
filesystem which served us excellently for many years.
rgds,
Harry + the team.
On 06/03/15 21:11, Dave Chinner wrote:
> On Fri, Mar 06, 2015 at 11:27:28AM +0000, Harry Percival wrote:
>> Glad we managed to nail down a probable culprit! Here's hoping
>> Debian and Ubuntu pull in a new kernel :)
>>
>> In other news, any advice on running this
>>
>> xfstests:src/bstat
>>
>> command as a way of estimating how long a quotacheck will take?
> It will give you an idea - quotacheck uses bulkstat, too.
>
>> Would it still be a useful estimator? Do you think it would
>> significantly affect the performance of a disk that's under fairly
>> heavy use?
> Of course. Bulkstat drives the disks as hard as they will go.
>
> Cheers,
>
> Dave.
--
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 prev parent reply other threads:[~2015-03-25 12:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 15:15 trying to avoid a lengthy quotacheck by deleting all quota data Harry
2015-02-24 16:39 ` 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 [this message]
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=5512AB38.7060009@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