public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: xfs.fsck change that is unhelpful
Date: Mon, 16 Aug 2010 04:44:08 -0500	[thread overview]
Message-ID: <4C690868.6040209@hardwarefreak.com> (raw)
In-Reply-To: <4C68A1CC.4050206@tlinx.org>

Linda Walsh put forth on 8/15/2010 9:26 PM:

>     That said -- how many people, who have their /home or /usr/people
> partition
> 'local' to their machine, automount it?  

I do.  Who wouldn't?  And why not?

/dev/sda6  /home     xfs   defaults   0     0
/dev/sda7  /samba    xfs   defaults   0     0


> I admit to thinking of the fsck
> field as having
> some meaning in the order in which file systems are mounted.  I guess
> that order is
> random now, though how I'm supposed to tell mount that '/home needs to
> be mounted
> only after "/", but need to be mounted before /home/share, without some
> ordering
> in fstab is something that is supposed to be specified....where?

The device mount order is defined by the lines in the fstab file.  Devices are
mounted in order, top to bottom, as each line is read.

>     I.e. isn't that field also the order in which file systems are
> mounted, or
> is there some other place that order is maintained other than in fstab?

>     Sorry, am definitely showing my ignorance in this area.

No need to apologize.  This is easily remedied by learning.  Start here:

      In general, file system mount order is determined by the order in which
the file systems appear in the fstab file. The exceptions to this ordering are
file systems mounted with the _netdev flag or filesystems that have their own
init scripts.

      A file system with its own init script is mounted later in the
initialization process, after the file systems in the fstab file.

      File systems mounted with the _netdev flag are mounted when the network
has been enabled on the system.

-- 
Stan

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2010-08-16  9:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-14 20:48 xfs.fsck change that is unhelpful Linda A. Walsh
2010-08-15  0:52 ` Dave Chinner
2010-08-15  2:03   ` Linda Walsh
2010-08-15 18:54     ` Hans-Peter Jansen
2010-08-15 22:43     ` Matthias Schniedermeyer
2010-08-16  1:55     ` Dave Chinner
2010-08-16  2:26       ` Linda Walsh
2010-08-16  9:44         ` Stan Hoeppner [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=4C690868.6040209@hardwarefreak.com \
    --to=stan@hardwarefreak.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