From: Diego Zuccato <diego.zuccato@unibo.it>
To: Eric Sandeen <sandeen@sandeen.net>, <linux-xfs@vger.kernel.org>
Subject: Re: Separate user- and project- quota ?
Date: Thu, 2 Jul 2020 08:14:01 +0200 [thread overview]
Message-ID: <cb98acba-ebbd-5b45-36bd-0ee292449615@unibo.it> (raw)
In-Reply-To: <9c64b36f-8222-a031-b458-9b15d8e6831f@sandeen.net>
Il 01/07/20 20:46, Eric Sandeen ha scritto:
> Hm, yes, worth a look. All 3 have been supported together for quite some
> time now, I didn't know it reacted badly on old filesystems.
> What did the failure look like?
Boot failure saying something about superblock not supporting both
group- and project- quotas at the same time.
I think it's related to
XFS (dm-0): Mounting V4 Filesystem
As I said, it' quite an old fs :)
xfs_info reports:
meta-data=/dev/sdb1 isize=256 agcount=41, agsize=268435455 blks
= sectsz=512 attr=2, projid32bit=0
= crc=0 finobt=0, sparse=0, rmapbt=0
= reflink=0
data = bsize=4096 blocks=10742852608, imaxpct=5
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0, ftype=0
log =internal log bsize=4096 blocks=521728, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
Too bad it's a production server (serving the home for the cluster) and
I can't down it now.
--
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786
next prev parent reply other threads:[~2020-07-02 6:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 10:58 Separate user- and project- quota ? Diego Zuccato
2020-06-28 18:22 ` Eric Sandeen
2020-07-01 8:41 ` Diego Zuccato
2020-07-01 18:46 ` Eric Sandeen
2020-07-02 6:14 ` Diego Zuccato [this message]
2020-07-02 11:34 ` Brian Foster
2020-07-02 12:15 ` Diego Zuccato
2020-07-02 12:50 ` Brian Foster
2020-07-04 15:21 ` Eric Sandeen
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=cb98acba-ebbd-5b45-36bd-0ee292449615@unibo.it \
--to=diego.zuccato@unibo.it \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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;
as well as URLs for NNTP newsgroup(s).