All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: david@lang.hm
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	xfs@oss.sgi.com, Christoph Hellwig <hch@infradead.org>,
	Justin Piszcz <jpiszcz@lucidpixels.com>,
	Alex Elder <aelder@sgi.com>, Mark Lord <kernel@teksavvy.com>,
	Stan Hoeppner <stan@hardwarefreak.com>
Subject: Re: xfs: very slow after mount, very slow at umount
Date: Sat, 29 Jan 2011 16:40:21 +1100	[thread overview]
Message-ID: <20110129054021.GB21311@dastard> (raw)
In-Reply-To: <alpine.DEB.2.00.1101281119250.17579@asgard.lang.hm>

On Fri, Jan 28, 2011 at 11:26:00AM -0800, david@lang.hm wrote:
> On Sat, 29 Jan 2011, Dave Chinner wrote:
> 
> >On Thu, Jan 27, 2011 at 06:09:58PM -0800, david@lang.hm wrote:
> >>On Thu, 27 Jan 2011, Stan Hoeppner wrote:
> >>>david@lang.hm put forth on 1/27/2011 2:11 PM:
> >>>
> >>>Picking the perfect mkfs.xfs parameters for a hardware RAID array can be
> >>>somewhat of a black art, mainly because no two vendor arrays act or perform
> >>>identically.
> >>
> >>if mkfs.xfs can figure out how to do the 'right thing' for md raid
> >>arrays, can there be a mode where it asks the users for the same
> >>information that it gets from the kernel?
> >
> >mkfs.xfs can get the information it needs directly from dm and md
> >devices. However, when hardware RAID luns present themselves to the
> >OS in an identical manner to single drives, how does mkfs tell the
> >difference between a 2TB hardware RAID lun made up of 30x73GB drives
> >and a single 2TB SATA drive? The person running mkfs should already
> >know this little detail....
> 
> that's my point, the person running mkfs knows this information, and
> can easily answer questions that mkfs asks (or provide this
> information on the command line). but mkfs doesn't ask for this
> infomation, instead it asks the user to define a whole bunch of
> parameters that are not well understood.

I'm going to be blunt - XFS is not a filesystem suited to use by
clueless noobs. XFS is a highly complex filesystem designed for high
end, high performance storage and therefore has the configurability
and flexibility required by such environments. Hence I expect that
anyone configuring an XFS filesystem for a production environments
is a professional and has, at minimum, done their homework before
they go fiddling with knobs. And we have a FAQ for a reason. ;)

> An XFS guru can tell you
> how to configure these parameters based on different hardware
> layouts, but as long as it remains a 'back art' getting new people
> up to speed is really hard. If this can be reduced down to
> 
> is this a hardware raid device
>   if yes
>     how many drives are there
>     what raid type is used (linear, raid 0, 1, 5, 6, 10)
>
> and whatever questions are needed, it would _greatly_ improve the
> quality of the settings that non-guru people end up using.

As opposed to just making mkfs DTRT without needing to ask
questions?

If you really think an interactive mkfs-for-dummies script is
necessary, then go ahead and write one - you don't need to modify
mkfs at all to do it.....

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: david@lang.hm
Cc: Stan Hoeppner <stan@hardwarefreak.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	xfs@oss.sgi.com, Christoph Hellwig <hch@infradead.org>,
	Justin Piszcz <jpiszcz@lucidpixels.com>,
	Alex Elder <aelder@sgi.com>, Mark Lord <kernel@teksavvy.com>
Subject: Re: xfs: very slow after mount, very slow at umount
Date: Sat, 29 Jan 2011 16:40:21 +1100	[thread overview]
Message-ID: <20110129054021.GB21311@dastard> (raw)
In-Reply-To: <alpine.DEB.2.00.1101281119250.17579@asgard.lang.hm>

On Fri, Jan 28, 2011 at 11:26:00AM -0800, david@lang.hm wrote:
> On Sat, 29 Jan 2011, Dave Chinner wrote:
> 
> >On Thu, Jan 27, 2011 at 06:09:58PM -0800, david@lang.hm wrote:
> >>On Thu, 27 Jan 2011, Stan Hoeppner wrote:
> >>>david@lang.hm put forth on 1/27/2011 2:11 PM:
> >>>
> >>>Picking the perfect mkfs.xfs parameters for a hardware RAID array can be
> >>>somewhat of a black art, mainly because no two vendor arrays act or perform
> >>>identically.
> >>
> >>if mkfs.xfs can figure out how to do the 'right thing' for md raid
> >>arrays, can there be a mode where it asks the users for the same
> >>information that it gets from the kernel?
> >
> >mkfs.xfs can get the information it needs directly from dm and md
> >devices. However, when hardware RAID luns present themselves to the
> >OS in an identical manner to single drives, how does mkfs tell the
> >difference between a 2TB hardware RAID lun made up of 30x73GB drives
> >and a single 2TB SATA drive? The person running mkfs should already
> >know this little detail....
> 
> that's my point, the person running mkfs knows this information, and
> can easily answer questions that mkfs asks (or provide this
> information on the command line). but mkfs doesn't ask for this
> infomation, instead it asks the user to define a whole bunch of
> parameters that are not well understood.

I'm going to be blunt - XFS is not a filesystem suited to use by
clueless noobs. XFS is a highly complex filesystem designed for high
end, high performance storage and therefore has the configurability
and flexibility required by such environments. Hence I expect that
anyone configuring an XFS filesystem for a production environments
is a professional and has, at minimum, done their homework before
they go fiddling with knobs. And we have a FAQ for a reason. ;)

> An XFS guru can tell you
> how to configure these parameters based on different hardware
> layouts, but as long as it remains a 'back art' getting new people
> up to speed is really hard. If this can be reduced down to
> 
> is this a hardware raid device
>   if yes
>     how many drives are there
>     what raid type is used (linear, raid 0, 1, 5, 6, 10)
>
> and whatever questions are needed, it would _greatly_ improve the
> quality of the settings that non-guru people end up using.

As opposed to just making mkfs DTRT without needing to ask
questions?

If you really think an interactive mkfs-for-dummies script is
necessary, then go ahead and write one - you don't need to modify
mkfs at all to do it.....

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2011-01-29  5:38 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-27  1:22 xfs: very slow after mount, very slow at umount Mark Lord
2011-01-27  1:43 ` Mark Lord
2011-01-27  3:43   ` Dave Chinner
2011-01-27  3:43     ` Dave Chinner
2011-01-27  3:53     ` Mark Lord
2011-01-27  3:53       ` Mark Lord
2011-01-27  4:54       ` Mark Lord
2011-01-27  4:54         ` Mark Lord
2011-01-27 23:34       ` Dave Chinner
2011-01-27 23:34         ` Dave Chinner
2011-01-27  3:30 ` Dave Chinner
2011-01-27  3:30   ` Dave Chinner
2011-01-27  3:49   ` Mark Lord
2011-01-27  3:49     ` Mark Lord
2011-01-27  5:17     ` Stan Hoeppner
2011-01-27 15:12     ` Mark Lord
2011-01-27 15:12       ` Mark Lord
2011-01-27 15:40       ` Justin Piszcz
2011-01-27 15:40         ` Justin Piszcz
2011-01-27 16:03         ` Mark Lord
2011-01-27 16:03           ` Mark Lord
2011-01-27 19:40           ` Stan Hoeppner
2011-01-27 19:40             ` Stan Hoeppner
2011-01-27 20:11             ` david
2011-01-27 20:11               ` david
2011-01-27 23:53               ` Stan Hoeppner
2011-01-27 23:53                 ` Stan Hoeppner
2011-01-28  2:09                 ` david
2011-01-28  2:09                   ` david
2011-01-28 13:56                   ` Dave Chinner
2011-01-28 13:56                     ` Dave Chinner
2011-01-28 19:26                     ` david
2011-01-28 19:26                       ` david
2011-01-29  5:40                       ` Dave Chinner [this message]
2011-01-29  5:40                         ` Dave Chinner
2011-01-29  6:08                         ` david
2011-01-29  6:08                           ` david
2011-01-29  7:35                           ` Dave Chinner
2011-01-29  7:35                             ` Dave Chinner
2011-01-31 19:17                             ` Christoph Hellwig
2011-01-31 19:17                               ` Christoph Hellwig
2011-01-27 21:56             ` Mark Lord
2011-01-27 21:56               ` Mark Lord
2011-01-28  0:17               ` Dave Chinner
2011-01-28  0:17                 ` Dave Chinner
2011-01-28  1:22                 ` Mark Lord
2011-01-28  1:22                   ` Mark Lord
2011-01-28  1:36                   ` Mark Lord
2011-01-28  1:36                     ` Mark Lord
2011-01-28  4:14                   ` David Rees
2011-01-28  4:14                     ` David Rees
2011-01-28 14:22                     ` Mark Lord
2011-01-28 14:22                       ` Mark Lord
2011-01-28  7:31                   ` Dave Chinner
2011-01-28  7:31                     ` Dave Chinner
2011-01-28 14:33                     ` Mark Lord
2011-01-28 14:33                       ` Mark Lord
2011-01-28 23:58                       ` Dave Chinner
2011-01-28 23:58                         ` Dave Chinner
2011-01-28 19:18             ` Martin Steigerwald
2011-01-28 19:18               ` Martin Steigerwald
2011-01-27 20:24           ` John Stoffel
2011-01-27 20:24             ` John Stoffel
2011-01-27 23:41       ` Dave Chinner
2011-01-27 23:41         ` Dave Chinner
2011-01-28  0:59         ` Mark Lord
2011-01-28  0:59           ` Mark Lord
2011-01-27 23:39     ` Dave Chinner
2011-01-27 23:39       ` Dave Chinner

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=20110129054021.GB21311@dastard \
    --to=david@fromorbit.com \
    --cc=aelder@sgi.com \
    --cc=david@lang.hm \
    --cc=hch@infradead.org \
    --cc=jpiszcz@lucidpixels.com \
    --cc=kernel@teksavvy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=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 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.