public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Harry <harry@pythonanywhere.com>, xfs@oss.sgi.com
Cc: "developers@pythonanywhere.com" <developers@pythonanywhere.com>
Subject: Re: trying to avoid a lengthy quotacheck by deleting all quota data
Date: Thu, 05 Mar 2015 11:44:26 -0600	[thread overview]
Message-ID: <54F895FA.4050205@sandeen.net> (raw)
In-Reply-To: <54F893AF.2070406@pythonanywhere.com>

On 3/5/15 11:34 AM, Harry wrote:
> We're on 3.13.0-39 (Ubuntu Trusty).
> 
> If you're interested in looking into it further, I'd be happy to provide any extra info you'd like?

Well, not really.  It all works here, and you have an ... interesting
setup, so if you've decided that somehow ext4 will save you from
quotachecks in the future, I'm not going to dig a lot further here.

I did already ask for logs, which might tell us why the original quota init
failed, but ... 

> But just to make sure I'm not wasting any of your time -- I think the
> team have pretty much decided to make the switch no matter what. The
> quotacheck issue is one thing, but actually the switch to ext4
> simplifies lots of other aspects of our quota system (one of the
> reasons we picked nfs was to be able to use project quotas, but it
> turns out we don't need them any more, so user quotas are simpler...)

... it sounds like you've already picked your solution to this AFAICT
not-well-understood problem.

*shrug* knock yourself out.  :)  You should use what works best meets your
needs, of course.

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2015-03-05 17:44 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 [this message]
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=54F895FA.4050205@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=developers@pythonanywhere.com \
    --cc=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