XFS Merged into Linux 2.4 265
Alphix writes "As noted on KernelTrap Marcelo has merged XFS into 2.4 after a code review by Christoph Hellwig. The mail from Marcelo on LKML is here. Apparently it touched very little VFS code so people not using XFS shouldn't see any ill effects from this (it's even supposed to fix some VFS bugs).
XFS is described by SGI as '...a journalling filesystem developed by SGI and used in SGI's IRIX operating system. It is now also available under GPL for linux. It is extremely scalable, using btrees extensively to support large and/or sparse files, and extremely large directories. The journalling capability means no more waiting for fsck's or worrying about meta-data corruption.' Let the stability vs. new-features flamewar begin."
ext3vs XFS? (Score:3, Interesting)
nowadays i use ext3 on my machines because it comes default with RH (by the way EL is now available for academia, woohoo!). hence my question:
can someone offer a nice comparison of ext3 versus XFS?
Re:ext3vs XFS? (Score:5, Informative)
Re:ext3vs XFS? (Score:3, Funny)
"Of course ext2 isn't a journaling filesystem and therefore it isn't a journaling filesystem and therefore has less advantages then xfs, jfs, reiserfs, ext3."
you see, i just find stupid stuff like this funny and therefore i just find stupid stuff like this funny. So sue me and sue me!
Re:ext3vs XFS? (Score:3, Insightful)
http://aurora.zemris.fer.hr/filesystems/
Th i s seems like a pretty poorly designed benchmark. One of the major tests was copying b/w two partitions (which is a valid test), but they put both partitions on the same disk! Whichever partition hapened to be allocated near the outside edge of the disk would have a clear advantage. Also it is not clear if the read, write, and delete portions of the test were done using the exact same partition or if some filesystems were handicapped by being on the
Re:ext3vs XFS? (Score:4, Informative)
Re:ext3vs XFS? (Score:3, Interesting)
Re:ext3vs XFS? (Score:5, Informative)
Yes [sgi.com].
Re:ext3vs XFS? (Score:2, Insightful)
Re:ext3vs XFS? (Score:3, Interesting)
For me, ext3 doesn't offer much data redundancy over plain old ext2. It still suffers from ext2's dataloss problems. Infact, with ext3, I had the horror of i/o errors. Once I had a bad powerdown, and I came close to reformatting just because it wouldn't let me into php.conf.
Personally, anyone looking for a data-redundancy fix should use ReiserFS (which we have had for a looong time), JFS or XFS.
Re:ext3vs XFS? (Score:2)
I would definatley not recommend reiserfs if you care about data. I've had atleast 2 occiasions where it lost data for no good reason. I would rather use ext2 than reiserfs any more, but when available I use XFS.
Re:ext3vs XFS? (Score:5, Informative)
Ext3 can grow or shrink an unmounted file system. XFS can grow a mounted file system.
Ext3 and XFS both have dump utilities, which many sys admins prefer for backup.
Ext3 supports three modes of journaling: writeback (risky metadata only), ordered (metadata only), and journal (all data). I believe XFS is comparable to ordered ext3.
Ext3 has been widely deployed on Linux, and it trivially reverts to ext2. The XFS design is mature, but its implementation on Linux is less proven.
Re:ext3vs XFS? (Score:3, Informative)
xfsdump on the other hand will work correctly.
Re:ext3vs XFS? (Score:5, Informative)
I'm not sure if xfsdump is any smarter about it because of the DMAPI stuff available, but I'd be carefull.
Re:ext3vs XFS? (Score:2)
Dumping a live file system can result in bad backups. Dump is best used on an unmounted file system. It can also work well with snapshots or split mirrors.
Re:ext3vs XFS? (Score:3, Informative)
Can't XFS also dynamically create more inodes? (Score:2)
AFAIK, ext3 can't, so when you run out, you get to backup, recreate the filesystem with more, then restore.
Quotas! (Score:3, Interesting)
No quotacheck (Score:2)
wait for a quotacheck on a huge filesystem.
Benchmarks (Score:4, Interesting)
I like xfs on the SGI - it's never let me down yet. I have to admit I'll be sorely tempted to try out xfs now that it's passed the 'seal-of-approval' and made it into the kernel - surely the best benchmark of all
Simon
Re:Benchmarks (Score:5, Informative)
Re:Benchmarks (Score:2)
Re:Benchmarks (Score:2)
Re:Benchmarks (Score:2)
Re:Benchmarks (Score:2, Informative)
Re:Benchmarks (Score:2)
Simon
Stability has been there for a long time. (Score:4, Informative)
It's already been stable for years, since VERY early in the 2.4.x cycle. It's just a detail in the naming that makes it merged as part of 2.4.x itself.
Careful with LILO (Score:5, Informative)
Q: Does LILO work with XFS?
This depens on where you install LILO. For MBR installation: Yes. For root partitions: No, because the XFS superblock goes where LILO would be installed. This is to maintain compatibility with the Irix on-disk format. This will not be changed. Putting the Superblock on the swap partition is reported to work but not guaranteed.
Re:Careful with LILO (Score:2, Insightful)
Re:Careful with LILO (Score:2)
Re:Careful with LILO (Score:2)
Re:Careful with LILO (Score:5, Informative)
GRUB is good. Boots anything. Wish we had OF.
Re:Careful with LILO (Score:2, Insightful)
Re:Careful with LILO (Score:2, Informative)
Re:Careful with LILO (Score:2)
for a start. SuSE (for example) have the support for all filesystems except ext2 in as modules. They use the initrd mechanism to load the rest of the stuff. This is not an approach I like - it means one more thing that can go horribly wrong if you compile your own kernel - but that is another matter.
Re:Careful with LILO (Score:2)
That simple exercise has saved me a couple of times.
Re:Careful with LILO (Score:2)
Re:Careful with LILO (Score:2)
Q: Does GRUB work with XFS?
Yes there is native XFS filesystem support for GRUB starting with version 0.91 and up. There is a GRUB rpm that supports XFS in the download section for the 1.0.2 installer on the FTP sites.
Re:Careful with LILO (Score:2)
Since the old days when there was a 1024 cylinder limit for the ROM BIOS and so for LILO, I usually have a very small partition (10 to 50 MBytes) somewhere in the first 1024 cylinders mounted at /boot. LILO is installed in that partition's super block, and the partition is marked active.
So if I would use XFS for / and other partitions, I still would keep that trusted little helper /boot partition with an ext2/ext3/minix/whatever filesystem that works with LILO.
Minor drawback: You have to uncomment export
An Overview (Score:5, Informative)
Re:An Overview (Score:3, Informative)
Comparison (Score:5, Informative)
XFS Rocks (Score:5, Informative)
Re:XFS Rocks (Score:2, Informative)
As of the patch for kernels 2.4.19+, acl support is very stable for ext[23]. In fact, I've been using it in production for over 2 years now. (I did help write some of the ext3-xattr+acl code, though, so maybe that means I'm a little bit more trusting of the code.)
The only big issues I've ever had is when using them in conjunction with quotas, but even when stress testing the filesystem, I
I love XFS (Score:4, Interesting)
Just one thing. Now that we've got the source code for dealing with xfs, can someone write a driver so I can mount my xfs partitions from windows xp? It would really help out a lot of us dual booting types. I would do it myself, but I don't know jack about how filesystems work. I just know which ones do what.
I hope they put the xfs into 2.6 also. Maybe it wont be necessary to have seperate xfs-sources in gentoo anymore and xfs will finally be included in the gentoo-sources.
Re:I love XFS (Score:3, Informative)
Re:I love XFS (Score:2)
Well, yeah, that's pretty much the gist of merging features into the kernel - distro maintainers don't have to patch them separately.
Re:I love XFS (Score:2)
I was going to paste a selection, but given that it seems to be ~250patches, I will just note that it's a LOT of patches :)
Re:I love XFS (Score:2)
If you were knocking MS specifically, depending on your level of conspiracy theory, you might even think it shows the opposite
Re:I love XFS (Score:2)
Re:I love XFS (Score:3, Interesting)
Not to mention fscking expensive. The regular DDK is free (for NT/2K) or cost of media (for the XP/2K3 DDKs), but the IFS Kit is $1000 US. And not well documented, from what I understand.
If anyone is going to try to write these for Windows, may I recommmend you check out OSR [osr.com]?
Disclaimer: No relation with OSR except as a satisfied client of their driver class.
its about time (Score:3, Interesting)
SCO (Score:5, Informative)
That is not the half of it. You see-- Hellwig is a former SCO employee who when he worked there, worked with IBM closely on their port of JFS to Linux. He was also heavily involved in the SMP development process too. Just do a search for his name and SCO and Caldera on your favorite search engine. I think it will be hard for him to avoid a deposition
Now he works for SGI.
Why so much fuss over JFS? (Score:3, Insightful)
If your box is crashing enough to make fscking a chore, you already have bigger problems. Sure, I can see where JFSs are sometimes useful, but on dekstops and most other machines the better-performing ext2 is a much more appropriate choice.
Re: Why so much fuss over JFS? (Score:2)
Quite the opposite in fact . .
. . . we're talking about different things here, aren't we?
Re:Why so much fuss over JFS? (Score:2)
In any case, when you have 500GB of filesystems, you really don't want to fsck that if a CPU fails.
Re:Why so much fuss over JFS? (Score:4, Informative)
Re:Why so much fuss over JFS? (Score:3, Informative)
Re:Why so much fuss over JFS? (Score:2)
if you are running a single IDE drive, then your data is not worth much. SCSI = worth a bit more... SCSI raid 5 with 4 drives and a journaling filesystem = worth alot more.
then we get to the level of hotplug scsi drives with tons of redundancy hardware raid 5 (works awesome with linux) and a real tape backup system (DLT) means your data is actually valuable....
and we can go up from there to extreme redundancy and data safety.
JFS = cheap security for valuable data...
Re:Why so much fuss over JFS? (Score:2)
Re:Why so much fuss over JFS? (Score:2)
Want another anecdotal data point about journaling filesystems? Windows NT from 5.x has a Journaling NTFS. (I've heard people say that NTFS has ALWAYS had some form of journaling, and that it wasn't turn
We've just begun (Score:3, Interesting)
I know we need the maximum user base for 2.6 testing, debugging and to recieve those "My TV stopped working when I installed kernel 2.6" messages. But we have to take it easy.
2.6 rocks. And a lot of distros have plans to release 2.6 based releases in the first quarter of 2004, which will greatly improve the user base.
IMHO, a good feature freeze, as Marcelo said somewhere in LKML, is 2.4.24 or even 2.4.25.
It's no time for a flamewar to begin. The Beaver is in the building.
I wonder (Score:2, Funny)
Patch size. (Score:4, Interesting)
bk6 - 424K
bk7 - 964k
bk8 - 1.2M
Well thats increased the kernel by about another 5-10%. However I would say I do like xfs and its proven quite stable now.
Rus
Christoph Hellwig, former SCO (Caldera)! (Score:5, Interesting)
Incidentally, this is the Christoph Hellwig who contributed code to the kernel on Calderas behalf. [groklaw.net] His contributions may become an important point in the SCO-IBM-RedHat battle.
YEAH, WOO HOOO - ALRIGHT! (Score:5, Informative)
We chose XFS after lots of serious testing. It beat all comers at the time and we've been using it ever since. The only downside to XFS is file deletion times are a bit long, especially compared to Reiser, but when you have a server that is uner HEAVY load (Databses, mail servers) and with LARGE files (log server) nothing beats XFS.
Thanks guys, this is one of those merges that has made me estatic!
Angry People Rule [angrypeoplerule.com]
Re: FINALLY! (Score:3, Interesting)
Re:YEAH, WOO HOOO - ALRIGHT! (Score:2)
Re:YEAH, WOO HOOO - ALRIGHT! (Score:3, Funny)
+JFS
Looks like they are pretty close. I think the only difference is the X and J.
No Complaints (Score:5, Informative)
It works with both GRUB and LILO, is reasonably speedy, and has enormous partition and file size limits.
Count me a happy customer.
~~LF
Oddly Enough (Score:5, Interesting)
SCO is going after SGI for XFS [linuxworld.com], when one of their own employees was working on it.
No. (Score:2)
Re:Oddly Enough (Score:2)
Groklaw said in the article that he 'also' had 2 e-mail addresses at SGI but not that he has been working for them for several months.
Finally (Score:3, Interesting)
Maybe this way RedHat begins to support it for their installations
Journals are for girls? (Score:5, Funny)
Huh? I always thought it was diaries that were for girls... at least, that's what I told my friends when they made fun of my journal.
Bechmarks (Score:4, Informative)
http://epoxy.mrs.umn.edu/~minerg/fstests/results.
Of course your mileage may vary but I generally got results consistent with those cited.
My own experiences (I have used both reiserfs and xfs with 2.4.20 kernel:
Re:Bechmarks (Score:2, Informative)
OTOH, I've been using XFS to store and edit 36-bit film scans (40+ MB file sizes) and XFS has been serving me extremely well, without data corruption of any kind - differently from Reiser 3, which needs a reiserfsck every time I boot Win2k
A few other nice XFS features (Score:5, Informative)
(from http://www.sgi.com/software/xfs/overview.html)
Guaranteed Rate I/O
XFS is the only file system available that provides a guaranteed rate I/O system, which allows applications to reserve specific bandwidth to or from the file system. The file system can determine the available bandwidth and guarantee that a requested level of performance is met for a given time. This functionality is critical for media delivery systems such as video-on-demand or data acquisition.
Expanded Dump Capabilities
Unlike traditional file systems, which must be dismounted to guarantee a consistent dump image, you can dump an XFS file system while it is being used. The XFS dump utility, XFSdump, can dump an entire filesystem, a directory tree, or specific files. XFSdump is restartable, which allows a large dump to be spread over an extended period of time or to be resumed after a system restart.
-->tech stuff [homelinux.net]
no GRIO on Linux (Score:4, Informative)
however, the realtime subvolume, which is a component of GRIO, is available for use on Linux.
Hmm.. (Score:2)
On a different note, I've been running XFS on my 2.6.0-test box for a while.. Now that it's going to be in a stable kernel, I can't wait to back up everything and switch. =D
NTFS not GPL, FAT not free (Score:4, Interesting)
Microsoft....hasn't. Heck, MS is preparing to charge media makers (CF, SM, MMC, etc) to use FAT.
I say media makers switch to using XFS or another GPL'd journaling file systems. Won't take long for other platforms to support it in bulk (make/ config.....) and for stuff like flash where corruptions can occur often, I'd like a bit of journaling to minimize the impact.
Re:NTFS not GPL, FAT not free (Score:3, Interesting)
ext2 on its own though....
Re:NTFS not GPL, FAT not free (Score:5, Informative)
Re:NTFS not GPL, FAT not free (Score:5, Informative)
Re:NTFS not GPL, FAT not free (Score:5, Informative)
This is not an endorsement of JFFS, it's just an example of a flash friendly journalling filesystem. (I have not used it - it may be the best filesystem ever, I don't know).
Re:NTFS not GPL, FAT not free (Score:3, Funny)
Bad web site. It's almost like they don't want anyone to try out their work. Another example of why developers should stick with developing and get their little nephews to put up their web sites for them.
Right, because a web site without a lot of nice colors and pictures might scare away my Grandma when she's looking for a new file system for the embedded Linux distro she's building. I mean, she really sees value in a file system that is compressed and offers near-optimal wear leveling while minimizing
Re: (Score:2)
Re:but NTFS (Score:2)
Re:I say what....? (Score:5, Interesting)
The main thing that keeps me on ext3 is ext2 backwards compatability. You dont have to worry about having custom repair/bootdisks to recognize your install, and its easier to do stuff like mount under windows (great for dual booting)
Re:I say what....? (Score:2)
In my testing, not good. But it makes a good server filesystem.
XFS seems to steal cycles from deep in the kernel itself therefore making it fairly fast for file operations but at the expense of everything else.
I didn't like it for a desktop system. It uses too much CPU and user responsiveness suffers.
Re:I say what....? (Score:5, Informative)
The btree-based storage structure is already employed by reiserfs in a similar manner, but XFS' implementation has been stable (used in IRIX) for quite a bit longer.
Re:I say what....? (Score:2)
Performance; scaleability (something around 9 million terabytes, if memory serves); stability - in the sense of a longer proven track-record - while ext3 is quite stable, XFS is simply a lot more mature; features, like ACLs and other small things.
Re:Vendor pressure (Score:3, Funny)
me i always h
Re:Vendor pressure (Score:3, Informative)
Marcelo probably shar
Re:Vendor pressure (Score:2, Informative)
It wasn't untill Cristoph OK'd the VFS changes that Marcello merged the XFS core.
SGI as a vendor has had nothing to do with it. Buy a altix 3000 and they would happily maintain any special patch you would need for that (IA64) machine.
I think I know what I'm talking about since it's my name on the XFS FAQ. And no I don't w
Hellwig's role in all this (Score:3, Interesting)
Now he works for SGI. The question I have is this-- it seems as if he has a conflict of interest to give his employer a beneficial review of the driver in order to ensure that it is included. I wonder how independent he is in his review.
That being said, he has been an important contributor to the kernel, and so I will give him the benefit of the doubt. I
Re:Wonder... (Score:2, Funny)
Re:XFS for Win32? (Score:2)
The second option would be ext2/3, since there is an installable FS driver that lets Windows NT mount ext2 partitions, although I haven't looked at the progress for a while.
The final option (the one I use) is to put your personal data on a cheap *NIX box (mine's FreeBSD box with a UFS disk) and SMB mount it for remote access under Windows
Re:XFS for Win32? (Score:3, Informative)
I guess you missed the article on Using the Real ntfs.sys Driver Under Linux [slashdot.org], eh?
Re:XFS for Win32? (Score:4, Informative)
Considering the difficulty in ensuring data integrity and support for B-tree arranged data, Microsoft would not look kindly upon XFS being ported to NT, since their next generation OS is supposed to include database like features to speed up indexing and accessing data like XFS already has built-in. It would really rain on their parade. Also, benchmarking shows NTFS is considerably slower than XFS (or FAT32 for that matter) for large files and NTFS has no support for Real-time I/O partitions or journals being located on separate disks.
NTFS also requires (according to ad-copy) constant defragmentation due to their primitive block allocation scheme while XFS does quite well even without the XFS FSR (File System Reorganizer). XFS's FSR was created for 1 specific customer who had a particular application that generated excessively fragmented disks. Before that, an FSR (/defragmenter) wasn't considered necessary because XFS is intelligent about how it lays out files when they are written and how it stores free space (with free space also stored in ordered B-tree's by powers-of-two size of the free space blocks.
The only benchmark I've seen XFS run noticeably slower on linux, on is deleting large numbers of small files -- something one doesn't notice on IRIX, since the space deallocation happens in background on IRIX, and only the inodes need be marked deleted before the user prompt returned. I seem to remember on Linux the space had to be deallocated synchronously for some reason or another.
Makes sense given the way free space is managed -- when files are deleted, free blocks are recursively combined with adjacent free blocks to create the largest possible 'free block size' (I think up to 128k blocks, default=4k block size) (my numbers may be a bit rusty). Free space blocks were combined asynchronously, under IRIX (as I understand it), in a system thread after the last reference to an inode was released. Linux, if I remember correctly, didn't support the facilities for such a background thread -- thus the block combining happens synchronously, explaining the performance hit for file tests that delete lots of small files: there are many small free blocks that are candidates for being merged with adjacent free space.
I'm not entirely sure why a special "XFS_del" process couldn't be started at system run time who's sole purpose was taking unreferenced inodes and doing the space combining in background, allowing foreground programs to continue asynchronously after simply marking the inode as unusable and enqueing it to the XFS "free space" combining process. It is quite possible some of this has been implemented and my information is dated. But free space combining on cleanup is one of the main reasons why, historically, XFS file systems, didn't need to have _continually_ running programs like Executive Software's, _DiskKeeper_, running, full time in background: because XFS had it's own built-in defragmentation every time a user did a file-delete.
For the degenerate case -- *one* customer was not getting sufficient speed for real-time, uncompressed video recording to disk (back in the early to mid 1990's when disks were much slower). The swat team, assigned to the problem, found that the customer's particular use kept many small files around while deleting some files in a way that prevented automatic space consolidation. This odd usage was just enough to slow down direct-to-disk video recording (something quite difficult on systems in the early to mid 90's when disks were not so fast and SCSI-2 was still state of the art). To solve this problem for *one* customer, the "xfs_fsr" util was written.
To make the most of the efforts spent on the one customer, SGI incorporated xfs_fsr into the general OS to be run occasionally to stave multi-month/year buildup of possible, similar degenerate cases. I.e. XFS customers considered fragmentation such an unlikely / non-issue, that the X
Re:Changes to the stable kernel? (Score:3, Informative)