From: Jan Engelhardt <jengelh@linux01.gwdg.de>
To: Nathan Scott <nathans@sgi.com>
Cc: ProfiHost - Stefan Priebe <s.priebe@profihost.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: XFS / Quota Bug in 2.6.17.x and 2.6.18x
Date: Sat, 29 Jul 2006 09:56:30 +0200 (MEST) [thread overview]
Message-ID: <Pine.LNX.4.61.0607290953480.20234@yvahk01.tjqt.qr> (raw)
In-Reply-To: <20060729075054.B2222647@wobbly.melbourne.sgi.com>
>> > The crash only occurs if you use quota and IDE without barrier support.
>>
>> I don't quite get this. I do use quota, and have barriers turned
>> off (either explicitly or because the drive does not support it),
>> but yet no error message like you posted. Do I just have luck?
>
>Heh, no - its more likely you just haven't needed to do a quotacheck
>on a filesystem thats initially mounted readonly (like root often is).
Well I "sometimes" do that, i.e. intentionally turning off quota on the
running system, to force a recheck on boot. The mount options essentially
are /bin/mount /dev/hda2 / -o ro,usrquota,grpquota and then /bin/mount / -o
remount,rw
No breakage so far, which is why I wondered. Is it limited to a specific
kernel version?
>I'm guessing you had quota enabled from earlier barrier-unaware kernels
>and quotacheck only needs to be run during that initial mount.
Jan Engelhardt
--
next prev parent reply other threads:[~2006-07-29 7:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 11:39 XFS / Quota Bug in 2.6.17.x and 2.6.18x ProfiHost - Stefan Priebe
2006-07-27 12:04 ` Alexey Dobriyan
2006-07-27 23:42 ` Nathan Scott
2006-07-28 17:11 ` Jan Engelhardt
2006-07-28 21:50 ` Nathan Scott
2006-07-29 7:56 ` Jan Engelhardt [this message]
2006-07-29 8:00 ` ProfiHost - Stefan Priebe
2006-07-29 8:02 ` Jan Engelhardt
2006-07-29 8:32 ` ProfiHost - Stefan Priebe
2006-07-29 15:14 ` Jan Engelhardt
2006-07-29 17:20 ` ProfiHost - Stefan Priebe
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=Pine.LNX.4.61.0607290953480.20234@yvahk01.tjqt.qr \
--to=jengelh@linux01.gwdg.de \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@sgi.com \
--cc=s.priebe@profihost.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;
as well as URLs for NNTP newsgroup(s).