All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Scobie <richard@sauce.co.nz>
To: xfs@oss.sgi.com
Subject: Re: xfs mount/create options (was: XFS status update for August 2010)
Date: Tue, 07 Sep 2010 10:55:14 +1200	[thread overview]
Message-ID: <4C857152.4060904@sauce.co.nz> (raw)

Michael Monnerie wrote:

 > When I defined su/sw on mkfs, is it enough, or would I always have to
 > specify sunit/swidth with every mount too?

Yes. sunit/swidth only needs to be added to your fstab if you either got 
the calculation wrong when you initially created the fs and wish to 
correct it, or if you grow the fs later over more drives.

Note that with recent kernels, mkfs.xfs will choose the optimal 
sunit/swidth for you if you are using md RAID or LVM (I believe the 
latter is correct).

Regards,

Richard

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

             reply	other threads:[~2010-09-06 22:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-06 22:55 Richard Scobie [this message]
2010-09-06 23:31 ` xfs mount/create options (was: XFS status update for August 2010) Michael Monnerie
  -- strict thread matches above, loose matches on Subject: below --
2010-09-02 14:59 XFS status update for August 2010 Christoph Hellwig
2010-09-05 10:47 ` Willy Tarreau
2010-09-05 13:08   ` Dave Chinner
2010-09-06  5:49     ` xfs mount/create options (was: XFS status update for August 2010) Michael Monnerie
2010-09-08  5:38       ` Michael Monnerie
2010-09-08 10:58         ` Dave Chinner
2010-09-08 13:38           ` Michael Monnerie
2010-09-08 14:51             ` Dave Chinner
2010-09-08 15:24               ` Emmanuel Florac
2010-09-08 23:34                 ` Michael Monnerie
2010-09-08 23:30               ` Michael Monnerie
2010-09-09  7:27                 ` Dave Chinner
2010-09-09  8:29                   ` Michael Monnerie

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=4C857152.4060904@sauce.co.nz \
    --to=richard@sauce.co.nz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.