linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: Michael Loftis <mloftis@wgops.com>
Cc: linux-xfs@oss.sgi.com, linux-lvm@redhat.com
Subject: Re: [linux-lvm] LVM onFly features
Date: Mon, 12 Dec 2005 09:15:39 +1100	[thread overview]
Message-ID: <20051211221539.GA872@frodo> (raw)
In-Reply-To: <64AE95D76D81F71989D42E79@dhcp-2-206.wgops.com>

On Sat, Dec 10, 2005 at 03:10:05PM -0700, Michael Loftis wrote:
> 
> >Thanks for the detailled explanation!
> 
> I try not to say something without actual experience and technical details 
> to back it up. :)

Hmm, you seem to be doing a pretty good job of that here...

> >Yes, I would *love* to use a totally new file system with a new,
> >dynamic, good design, but - just as many others - had my experiences
> >with ReiserFS and it will take a *lot* of time for ReiserFS to restore
> >confidence. So for now, I'll probably stay with ext3, with which I had
> >no problems so far.
> >
> >JFS/XFS should also both be capable of growing, XFS of online-growth,
> >IIRC.
> 
> XFS has terrible unpredictable performance in production.  Also it has very 

What on earth does that mean?  Whatever it means, it doesn't
sound right - can you back that up with some data please?

> bad behavior when recovering from crashes,

Details?  Are you talking about this post of yours:
http://oss.sgi.com/archives/linux-xfs/2003-06/msg00032.html

There have been several fixes in this area since that post.

> often times it's tools totally fail to clean the filesystem.

In what way?  Did you open a bug report?

> It also needs larger kernel stacks because 
> of some of the really deep call trees,

Those have been long since fixed as far as we are aware.  Do you
have an actual example where things can fail?

> so when you use it with LVM or MD it 
> can oops unless you use the larger kernel stacks.

Anything can oops in combination with enough stacked device drivers
(although there has been block layer work to resolve this recently,
so you should try again with a current kernel...).  If you have an
actual example of this still happening, please open a bug or at least
let the XFS developers know of your test case.  Thanks.

> We also have had 
> problems with the quota system but the details on that have faded.

Seems like details of all the problems you described have faded.
Your mail seems to me like a bit of a troll ... I guess you had a
problem or two a couple of years ago (from searching the lists)
and are still sore.  Can you point me to mailing list reports of
the problems you're refering to here or bug reports you've opened
for these issues?  I'll let you know if any of them are still
relevent.

cheers.

-- 
Nathan

  parent reply	other threads:[~2005-12-11 22:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-10 19:38 [linux-lvm] LVM onFly features Mag Gam
2005-12-10 19:48 ` Marc-Jano Knopp
2005-12-10 20:03   ` Michael Loftis
2005-12-10 20:06     ` Marc-Jano Knopp
2005-12-10 20:14       ` Michael Loftis
2005-12-10 20:22         ` Marc-Jano Knopp
2005-12-10 22:10           ` Michael Loftis
2005-12-10 22:31             ` Marc-Jano Knopp
2005-12-10 22:44               ` Michael Loftis
2005-12-10 22:51                 ` Michael Loftis
2005-12-10 23:03                   ` Marc-Jano Knopp
2005-12-11  3:38                     ` Mag Gam
2005-12-11  7:43                       ` Michael Loftis
2005-12-11 14:08                       ` Fredrik Tolf
2005-12-11 15:32                         ` Mag Gam
2005-12-15 20:44                           ` David Johnston
2005-12-18  0:27                             ` Mag Gam
2005-12-11 22:15             ` Nathan Scott [this message]
2005-12-12  1:14               ` Michael Loftis
2005-12-12  2:28                 ` Nathan Scott
2005-12-10 20:47         ` Graham Wood
2005-12-13 16:56         ` Stephen C. Tweedie

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=20051211221539.GA872@frodo \
    --to=nathans@sgi.com \
    --cc=linux-lvm@redhat.com \
    --cc=linux-xfs@oss.sgi.com \
    --cc=mloftis@wgops.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;
as well as URLs for NNTP newsgroup(s).