Skip to contentSkip to conversation

XFS?

DISCUSSION Martin Knoblauch 5 participants 8 messages Sep 12, 2002

lore
Share & tools
lore
#0 lore raw
Quoted 3 lines
Quoted 3 lines

In my opinion the non-inclosure in the mainline kernel is the most important reason not to use XFS (or any other FS). Which in turn massively reduces the tester base. It is a shame, because for some

type

Quoted 10 lines
Quoted 1 line

of applications it performs great, or better than anything else.

On the other hand, filesystem corruption bugs are one of the worst type to suffer from. We absolutely don't want to include filesystems without at least a reasonable proven track record in the mainline kernel, and therefore encourage the various distributions to use them, incase any bugs do show up. Look how long a buffer overflow existed in Zlib unnoticed.

If enclosure in "major" distribuitons defines mainline for you, I have
to agree. Otherwise, how do you get "a proven track record in mainline" without having it in the mainline kernel ? :-)

In any case, one could always mark XFS as "experimental" for some time.

Quoted 4 lines

EXT2 is a very capable filesystem, and has *years* of proven reliability. That's why I'm not going to switch away from it for critical work any time soon.

sure, if you can live with the fsck time on your 200 GB (or bigger)
filesystem after the occasional crash.

Martin

Signature · 10 lines
Martin Knoblauch
Senior System Architect
MSC.software GmbH
Am Moosfeld 13
D-81829 Muenchen, Germany

e-mail: [email protected]
http://www.mscsoftware.com
Phone/Fax: +49-89-431987-189 / -7189
Mobile: +49-174-3069245
#1 lore raw
Quoted 14 lines
Quoted 3 lines
Quoted 3 lines

In my opinion the non-inclosure in the mainline kernel is the most important reason not to use XFS (or any other FS). Which in turn massively reduces the tester base. It is a shame, because for some

type

Quoted 9 lines
Quoted 1 line

of applications it performs great, or better than anything else.

On the other hand, filesystem corruption bugs are one of the worst type to suffer from. We absolutely don't want to include filesystems without at least a reasonable proven track record in the mainline kernel, and therefore encourage the various distributions to use them, incase any bugs do show up. Look how long a buffer overflow existed in Zlib unnoticed.

Quoted 3 lines

If enclosure in "major" distribuitons defines mainline for you, I have to agree. Otherwise, how do you get "a proven track record in mainline" without having it in the mainline kernel ? :-)

Sorry, I meant we should be wary about what is moved from being development code to non-development code in the stable kernel.

Quoted 1 line

In any case, one could always mark XFS as "experimental" for some time.

Exactly, I think we should.

The distributions will 'mirror' that, by including support, but not making it obvious unless you poke around looking for it - so it gets the new feature out to the more users, but doesn't present it as just another option for newbies to select without realising what they are doing.

Quoted 6 lines
Quoted 3 lines

EXT2 is a very capable filesystem, and has *years* of proven reliability. That's why I'm not going to switch away from it for critical work any time soon.

sure, if you can live with the fsck time on your 200 GB (or bigger) filesystem after the occasional crash.

But Linux doesn't crash... :-)

John.

#2 lore raw

Hi,

Quoted 1 line · On Thu, 12 Sep 2002 [email protected] wrote:

But Linux doesn't crash... :-)

I'm running 2.4.19-rc5-aa1 on reiserfs on some twenty workstations, neither of which ever crashed...

Thunder

Signature · 4 lines
--./../...-/. -.--/---/..-/.-./..././.-../..-. .---/..-/.../- .-
--/../-./..-/-/./--..-- ../.----./.-../.-.. --./../...-/. -.--/---/..-
.- -/---/--/---/.-./.-./---/.--/.-.-.-
--./.-/-.../.-./.././.-../.-.-.-
#3 lore raw

Quoting Thunder from the hill <[email protected]>:

Quoted 8 lines

Hi,

Quoted 1 line · On Thu, 12 Sep 2002 [email protected] wrote:

But Linux doesn't crash... :-)

I'm running 2.4.19-rc5-aa1 on reiserfs on some twenty workstations, neither of which ever crashed...

Alot of hosting companies employ the "pull the plug" method of solving problems. This isnt good on non journaling filesystems. (It's not good period, but thats not going to change anytime soon).

-------------------------------------------------
sent via KingsMeade secure webmail http://www.kingsmeadefarm.com

#4 lore raw

Hi,

Quoted 3 lines · Joe Kellner

Alot of hosting companies employ the "pull the plug" method of solving problems. This isnt good on non journaling filesystems. (It's not good period, but thats not going to change anytime soon).

I don't see where reiserfs isn't journaling.

Thunder

Signature · 4 lines
--./../...-/. -.--/---/..-/.-./..././.-../..-. .---/..-/.../- .-
--/../-./..-/-/./--..-- ../.----./.-../.-.. --./../...-/. -.--/---/..-
.- -/---/--/---/.-./.-./---/.--/.-.-.-
--./.-/-.../.-./.././.-../.-.-.-
#5 lore raw

Quoting Thunder from the hill <[email protected]>:

Quoted 6 lines

Hi,

I don't see where reiserfs isn't journaling.

That was speaking of EXT2, not ReiserFS. Sorry for the confusion.

-------------------------------------------------
sent via KingsMeade secure webmail http://www.kingsmeadefarm.com

#6 lore raw
In reply to [email protected]

[email protected] wrote:
[...]

Quoted 4 lines
Quoted 2 lines

sure, if you can live with the fsck time on your 200 GB (or bigger) filesystem after the occasional crash.

But Linux doesn't crash... :-)

Just pull the power cable out of your PC and see what happens.

Bernd

Signature · 4 lines
Bernd Petrovitsch                              Email : [email protected]
g.a.m.s gmbh                                  Fax : +43 1 205255-900
Prinz-Eugen-Straße 8                    A-1040 Vienna/Austria/Europe
                     LUGA : http://www.luga.at
#7 lore raw

Hi,

Quoted 3 lines · Bernd Petrovitsch
Quoted 1 line

But Linux doesn't crash... :-)

Just pull the power cable out of your PC and see what happens.

The UPS starts beeping.

Thunder

Signature · 4 lines
--./../...-/. -.--/---/..-/.-./..././.-../..-. .---/..-/.../- .-
--/../-./..-/-/./--..-- ../.----./.-../.-.. --./../...-/. -.--/---/..-
.- -/---/--/---/.-./.-./---/.--/.-.-.-
--./.-/-.../.-./.././.-../.-.-.-