From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@oss.sgi.com, Marcos Mello <marcosfrm@gmail.com>
Subject: Re: Placing the root partition on an XFS filesystem is not supported
Date: Sun, 05 Feb 2012 19:58:00 -0600 [thread overview]
Message-ID: <4F2F33A8.1050403@sandeen.net> (raw)
In-Reply-To: <20120206015430.GK6922@dastard>
On 2/5/12 7:54 PM, Dave Chinner wrote:
> On Sun, Feb 05, 2012 at 06:13:28PM -0600, Eric Sandeen wrote:
>> On 2/5/12 6:11 PM, Dave Chinner wrote:
>>> On Fri, Feb 03, 2012 at 12:50:17PM -0600, Eric Sandeen wrote:
>>>> On 2/3/12 8:39 AM, Marcos Mello wrote:
>>>>> Eric Sandeen <sandeen <at> sandeen.net> writes:
>>>>>
>>>>>>
>>>>>> In general there is no problem with xfs on a root partition. However, the
>>>>> installer
>>>>>> may not make it easy or available for you.
>>>>>>
>>>>>> (I never use xfs for /boot though, I don't trust grub enough for that
>>>>> honestly).
>>>>>>
>>>>>> -Eric
>>>>>
>>>>> Same thing on Fedora 16. Let's hope some day Anaconda will change that.
>>>>
>>>> F16 prevents it? I didn't see it in the upstream tree. That should
>>>> not be so. :/
>>>>
>>>>> About GRUB with a XFS /boot the problem was with GRUB Lagacy, wasn't it?
>>>>> Or GRUB2 is still buggy?
>>>>
>>>> I have no idea, actually. I delved into grub a bit, it was disturbing
>>>> enough that I have not tried to look at grub2. :)
>>>
>>> Certainly the problem exists with legacy grub - it assumes that it
>>> can write to the first sector or any disk or partition which
>>> overwrites the XFS superblock...
>>
>> well, it was worse than that. I can work around the grub-on-a-partition
>> problem, but what I ran into was grub reading & writing to/from the block
>> device under a mounted filesystem - corruption and hilarity ensued.
>
> Oh, grub2 does worse things than that - grub_probe mounts any device
> that appears to have a valid superblock so it can find out what
> devices it needs to list in it's boot menu. I found this out when I
> built a big DM stripe out of disks that used to have filesystems on
> them. grub-probe mounted every single device -inside- the stripe
> and ran log recovery on them, corrupting the new filesystem and
> quite a bit of data on the DM stripe they were part of....
Ok, your horror story wins from a pain POV ;)
but sounds like someone should have zeroed out a bit more disk
when setting up the dm stripes :(
I've always thought maybe we needed a libzero.so to zap every known signature
on disk....
-Eric
> Cheers,
>
> Dave.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-02-06 1:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 12:46 Placing the root partition on an XFS filesystem is not supported Marcos Mello
2012-01-30 9:12 ` Stan Hoeppner
2012-01-30 11:19 ` Marcos Mello
2012-02-02 21:40 ` Eric Sandeen
2012-02-03 14:39 ` Marcos Mello
2012-02-03 18:50 ` Eric Sandeen
2012-02-06 0:11 ` Dave Chinner
2012-02-06 0:13 ` Eric Sandeen
2012-02-06 1:54 ` Dave Chinner
2012-02-06 1:58 ` Eric Sandeen [this message]
2012-02-06 3:29 ` Stan Hoeppner
2012-02-06 10:44 ` Marcos Mello
-- strict thread matches above, loose matches on Subject: below --
2012-02-04 4:17 Richard Scobie
2012-02-04 14:29 ` Marcos Mello
2012-02-05 0:47 ` 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=4F2F33A8.1050403@sandeen.net \
--to=sandeen@sandeen.net \
--cc=david@fromorbit.com \
--cc=linux-xfs@oss.sgi.com \
--cc=marcosfrm@gmail.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