public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ProfiHost - Stefan Priebe <s.priebe@profihost.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Nathan Scott <nathans@sgi.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 19:20:55 +0200	[thread overview]
Message-ID: <44CB98F7.9070900@profihost.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0607291714070.24901@yvahk01.tjqt.qr>

Hi!

Correct - it only happens, if you use rootflags=quota without initrd.

Stefan


Jan Engelhardt schrieb:
>>1.) You need a Kernel, where barriers are on by default:
>>so something like: 2.6.16.2x or 2.6.17.x
>>I'm not shure of the minimal version for the 2.6.16.x Kernel tree.
> 
> 
> 2.6.17.6
> 
> 
>>3.) you boot your system with kernel option rootflags=quota
> 
> 
> Ah I think there it is. I do boot with rootflags=, but since the initrd 
> does the interpreting of rootflags= and mounting of /dev/hda2(/), that 
> should pose a different situation?
> 
> 
> Jan Engelhardt

      reply	other threads:[~2006-07-29 17:21 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
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 [this message]

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=44CB98F7.9070900@profihost.com \
    --to=s.priebe@profihost.com \
    --cc=adobriyan@gmail.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathans@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