From: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
To: xfs@oss.sgi.com
Subject: Re: weird quota issue
Date: Tue, 23 Dec 2014 08:19:20 +0100 [thread overview]
Message-ID: <201412230819.20935.arekm@maven.pl> (raw)
In-Reply-To: <20141223024248.GC4521@dastard>
On Tuesday 23 of December 2014, Dave Chinner wrote:
> On Tue, Dec 23, 2014 at 02:12:15AM +0000, Weber, Charles (NIH/NIA/IRP) [E]
wrote:
> > here you go
> >
> > # xfs_db -c "inode 131" -c p /dev/dm-7
>
> Nothing obviously wrong there, so there's no clear indication of why
> the quota initialisation failed.
gquotino should be set to null, setting it via xfs_db should fix the problem
> uquotino = 131
> gquotino = 0
> qflags = 0
Otherwise we end up with my last problem
http://oss.sgi.com/archives/xfs/2014-07/msg00121.html
"- 3.10 kernel is not able to handle case when uquotino == value, gquotino ==
0. For 3.10 this case is impossible / should never happen. 3.10 expects
(uquotino == value, gquotino == null) or (uquotino == value, gquotino ==
othervalue) or (uqotinfo == null, gruotino == value) only."
So I guess 2.6.32 is doing the same.
AFAIK xfs_repair doesn't fix this issue. Not sure.
> Dave.
--
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-12-23 7:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 21:26 weird quota issue Weber, Charles (NIH/NIA/IRP) [E]
2014-12-22 16:34 ` Charles Weber
2014-12-22 20:48 ` Dave Chinner
2014-12-22 22:13 ` Weber, Charles (NIH/NIA/IRP) [C]
2014-12-22 22:35 ` Dave Chinner
2014-12-22 22:46 ` Weber, Charles (NIH/NIA/IRP) [C]
2014-12-23 0:32 ` Dave Chinner
2014-12-23 2:12 ` Weber, Charles (NIH/NIA/IRP) [E]
2014-12-23 2:42 ` Dave Chinner
2014-12-23 7:19 ` Arkadiusz Miśkiewicz [this message]
2014-12-23 20:35 ` Dave Chinner
2014-12-23 16:31 ` Weber, Charles (NIH/NIA/IRP) [C]
2014-12-23 18:48 ` Weber, Charles (NIH/NIA/IRP) [C]
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=201412230819.20935.arekm@maven.pl \
--to=arekm@maven.pl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.