public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: MusicMan529@yahoo.com
Cc: xfs@oss.sgi.com
Subject: Re: XFS w/ extern journal as root on Linux?
Date: Thu, 26 Jun 2008 00:14:32 -0500	[thread overview]
Message-ID: <486325B8.5010505@sandeen.net> (raw)
In-Reply-To: <732501.9968.qm@web34508.mail.mud.yahoo.com>

Mark wrote:
> Well, I tried to convert my non-/home space to XFS with an external journal, but Linux consistently choked on it. I passed "rootfstype=xfs root=/dev/sdb5 rootflags=logdev=/dev/sda2" on the kernel command line (via GRUB) but it panicked every time. 
> 
> Here is a transcript of the boot panic from an unmodified kernel:
> 
> ~~~~~~~~~~~~~~~~~
> md: Autodetecting RAID arrays.
> md: Scanned 0 and added 0 devices.
> md: autorun ...
> md: ... autorun DONE.
> XFS: Invalid device [/dev/sda2], error=-2

Hm, xfs wants to open it by name ("/dev/sda2") but if we look at the
early mount stuff it's doing essentially:

	root_device_name = saved_root_name; /* from root= */

        ROOT_DEV = name_to_dev_t(root_device_name);

        create_dev("/dev/root", ROOT_DEV);
        mount_block_root("/dev/root", root_mountflags);

so it's creating its own dev to open, and this isn't done for the logdev.

I wonder if xfs can do similar tricks, or maybe do name_to_dev_t and do
the open by dev_t not path?

This is probably where somebody tells me I'm wrong for the following
reasons: a, b, c, ... :)

-Eric

      reply	other threads:[~2008-06-26  5:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26  4:50 XFS w/ extern journal as root on Linux? Mark
2008-06-26  5:14 ` Eric Sandeen [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=486325B8.5010505@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=MusicMan529@yahoo.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox