<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: XFS vs Reiser</title>
	<atom:link href="http://pthree.org/2008/04/23/xfs-vs-reiser/feed/" rel="self" type="application/rss+xml" />
	<link>http://pthree.org/2008/04/23/xfs-vs-reiser/</link>
	<description>Linux.  GNU.  Freedom.</description>
	<lastBuildDate>Fri, 17 May 2013 20:46:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.6-beta2-24176</generator>
	<item>
		<title>By: Alex</title>
		<link>http://pthree.org/2008/04/23/xfs-vs-reiser/#comment-108836</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Thu, 23 Oct 2008 20:48:50 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=568#comment-108836</guid>
		<description><![CDATA[As Will stated, XFS require tuning for performance. This webpage is quite interesting

http://everything2.com/node/1479435

Personally, I haven&#039;t tried XFS, but it sounds quite good...]]></description>
		<content:encoded><![CDATA[<p>As Will stated, XFS require tuning for performance. This webpage is quite interesting</p>
<p><a href="http://everything2.com/node/1479435" rel="nofollow">http://everything2.com/node/1479435</a></p>
<p>Personally, I haven&#8217;t tried XFS, but it sounds quite good&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: will</title>
		<link>http://pthree.org/2008/04/23/xfs-vs-reiser/#comment-106895</link>
		<dc:creator>will</dc:creator>
		<pubDate>Mon, 25 Aug 2008 08:39:10 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=568#comment-106895</guid>
		<description><![CDATA[I like them all. Some require tuning for good performance, expecially xfs, and some don&#039;t work well with some kernels.

my personal
/dev/hda5 on / type reiserfs (rw,noatime,data=writeback,notail)
/proc on /proc type proc (rw)
/sys on /sys type sysfs (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/hda8 on /1 type reiser4 (rw,noatime)
/dev/hdi3 on /2 type xfs (rw,noatime,nodiratime,logbufs=4,logbsize=256k)
/dev/hda10 on /4 type jfs (rw,noatime,nodiratime)
tmpfs on /dev/shm type tmpfs (rw)]]></description>
		<content:encoded><![CDATA[<p>I like them all. Some require tuning for good performance, expecially xfs, and some don&#8217;t work well with some kernels.</p>
<p>my personal<br />
/dev/hda5 on / type reiserfs (rw,noatime,data=writeback,notail)<br />
/proc on /proc type proc (rw)<br />
/sys on /sys type sysfs (rw)<br />
none on /dev/pts type devpts (rw,gid=5,mode=620)<br />
/dev/hda8 on /1 type reiser4 (rw,noatime)<br />
/dev/hdi3 on /2 type xfs (rw,noatime,nodiratime,logbufs=4,logbsize=256k)<br />
/dev/hda10 on /4 type jfs (rw,noatime,nodiratime)<br />
tmpfs on /dev/shm type tmpfs (rw)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jimcooncat</title>
		<link>http://pthree.org/2008/04/23/xfs-vs-reiser/#comment-99582</link>
		<dc:creator>jimcooncat</dc:creator>
		<pubDate>Tue, 29 Apr 2008 11:52:41 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=568#comment-99582</guid>
		<description><![CDATA[Update 4/29/08: John Dong (jdong) has enlightened me regarding the waning support of ReiserFS. The website of the developing company, Namesys, has now gone offline. OpenSUSE did have good reasons to stop using it as the default filesystem, and I wished I&#039;d run across their reasoning earlier (link below). I&#039;m reevaluating, and will probably start using Ext3 instead.

http://blog.linuxoss.com/2006/09/27/suse-102-ditching-reiserfs-as-it-default-fs/]]></description>
		<content:encoded><![CDATA[<p>Update 4/29/08: John Dong (jdong) has enlightened me regarding the waning support of ReiserFS. The website of the developing company, Namesys, has now gone offline. OpenSUSE did have good reasons to stop using it as the default filesystem, and I wished I&#8217;d run across their reasoning earlier (link below). I&#8217;m reevaluating, and will probably start using Ext3 instead.</p>
<p><a href="http://blog.linuxoss.com/2006/09/27/suse-102-ditching-reiserfs-as-it-default-fs/" rel="nofollow">http://blog.linuxoss.com/2006/09/27/suse-102-ditching-reiserfs-as-it-default-fs/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trevor</title>
		<link>http://pthree.org/2008/04/23/xfs-vs-reiser/#comment-99522</link>
		<dc:creator>Trevor</dc:creator>
		<pubDate>Mon, 28 Apr 2008 23:05:19 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=568#comment-99522</guid>
		<description><![CDATA[Guess this solves the whole debate.

http://blog.wired.com/27bstroke6/2008/04/reiser-guilty-o.html

ReiserFS will start to fade away.]]></description>
		<content:encoded><![CDATA[<p>Guess this solves the whole debate.</p>
<p><a href="http://blog.wired.com/27bstroke6/2008/04/reiser-guilty-o.html" rel="nofollow">http://blog.wired.com/27bstroke6/2008/04/reiser-guilty-o.html</a></p>
<p>ReiserFS will start to fade away.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anthony</title>
		<link>http://pthree.org/2008/04/23/xfs-vs-reiser/#comment-98859</link>
		<dc:creator>Anthony</dc:creator>
		<pubDate>Thu, 24 Apr 2008 03:49:26 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=568#comment-98859</guid>
		<description><![CDATA[I have to agree with jdong and most of the others about XFS.  It&#039;s certainly not good (possibly very poor) for regular desktop filesystem partitions, but I&#039;ve been using it for years on my storage drive(s) without any problems.  It&#039;s varied from 200gb drive up to a ~1 tb RAID 5 array....   holding movies, mp3&#039;s, backup tar archives, and other large files it excels greatly at.  Never had any corruption issues in the past 5-6 years I&#039;ve used it.  It also excels at very large partitions and guaranteed I/O rate.  Supposedly JFS is somewhat decent at this as well but cannot give any real experience.

I&#039;ve actually heard ReiserFS was the worst for stability issues although this was at some time ago.  Have not used it but know it&#039;s fast for large amounts of small files especially with lots of creation/deletions.... /var or /tmp perhaps?

Personally use XFS on my fileserver RAID array (running NFS) and ext3 for all partitions on all other boxes.  Highly recommend against using ext3 for any large partitions, tried it - it&#039;s crazy slow.]]></description>
		<content:encoded><![CDATA[<p>I have to agree with jdong and most of the others about XFS.  It&#8217;s certainly not good (possibly very poor) for regular desktop filesystem partitions, but I&#8217;ve been using it for years on my storage drive(s) without any problems.  It&#8217;s varied from 200gb drive up to a ~1 tb RAID 5 array&#8230;.   holding movies, mp3&#8242;s, backup tar archives, and other large files it excels greatly at.  Never had any corruption issues in the past 5-6 years I&#8217;ve used it.  It also excels at very large partitions and guaranteed I/O rate.  Supposedly JFS is somewhat decent at this as well but cannot give any real experience.</p>
<p>I&#8217;ve actually heard ReiserFS was the worst for stability issues although this was at some time ago.  Have not used it but know it&#8217;s fast for large amounts of small files especially with lots of creation/deletions&#8230;. /var or /tmp perhaps?</p>
<p>Personally use XFS on my fileserver RAID array (running NFS) and ext3 for all partitions on all other boxes.  Highly recommend against using ext3 for any large partitions, tried it &#8211; it&#8217;s crazy slow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Wegner</title>
		<link>http://pthree.org/2008/04/23/xfs-vs-reiser/#comment-98825</link>
		<dc:creator>Scott Wegner</dc:creator>
		<pubDate>Wed, 23 Apr 2008 22:49:05 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=568#comment-98825</guid>
		<description><![CDATA[I plan on reformatting my HDD next week and starting anew when stable Hardy comes out.  As such, it&#039;s one of my goals to try out new filesystems to fit my needs.  Previously I&#039;ve been dual-booting, so I had ext3 for Ubuntu partition, and NTFS for data.  But, I&#039;d like to try ReiserFS for the Linux partition, and perhaps XFS or JFS for the data partition.  I use MythTV and store a lot of large video files on the data partition, so I&#039;ve heard XFS and JFS are both good options.  Is one better than the other?]]></description>
		<content:encoded><![CDATA[<p>I plan on reformatting my HDD next week and starting anew when stable Hardy comes out.  As such, it&#8217;s one of my goals to try out new filesystems to fit my needs.  Previously I&#8217;ve been dual-booting, so I had ext3 for Ubuntu partition, and NTFS for data.  But, I&#8217;d like to try ReiserFS for the Linux partition, and perhaps XFS or JFS for the data partition.  I use MythTV and store a lot of large video files on the data partition, so I&#8217;ve heard XFS and JFS are both good options.  Is one better than the other?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jldugger</title>
		<link>http://pthree.org/2008/04/23/xfs-vs-reiser/#comment-98802</link>
		<dc:creator>jldugger</dc:creator>
		<pubDate>Wed, 23 Apr 2008 19:14:21 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=568#comment-98802</guid>
		<description><![CDATA[Unless you have redundant power, I&#039;d stick with with ext3. Like Kees, I&#039;ve seen XFS corrupt data on power failure.  The FAQ on the subject used to say &quot;If it hurts, don&#039;t do it&quot; as if the only reason this happened was people forcing power off.

If you&#039;re really after benchmarking etc, it might be informative to the general Linux using public to examine multiple versions of ext4, as we can expect the performance characteristics to change over time.]]></description>
		<content:encoded><![CDATA[<p>Unless you have redundant power, I&#8217;d stick with with ext3. Like Kees, I&#8217;ve seen XFS corrupt data on power failure.  The FAQ on the subject used to say &#8220;If it hurts, don&#8217;t do it&#8221; as if the only reason this happened was people forcing power off.</p>
<p>If you&#8217;re really after benchmarking etc, it might be informative to the general Linux using public to examine multiple versions of ext4, as we can expect the performance characteristics to change over time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott James Remnant</title>
		<link>http://pthree.org/2008/04/23/xfs-vs-reiser/#comment-98778</link>
		<dc:creator>Scott James Remnant</dc:creator>
		<pubDate>Wed, 23 Apr 2008 16:19:48 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=568#comment-98778</guid>
		<description><![CDATA[...and if you&#039;re after your data, use ext3]]></description>
		<content:encoded><![CDATA[<p>&#8230;and if you&#8217;re after your data, use ext3</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kees Cook</title>
		<link>http://pthree.org/2008/04/23/xfs-vs-reiser/#comment-98776</link>
		<dc:creator>Kees Cook</dc:creator>
		<pubDate>Wed, 23 Apr 2008 16:15:51 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=568#comment-98776</guid>
		<description><![CDATA[I have to agree with most people here.

XFS: I have seen repeated, disastrous, corruptions with XFS.  It has eaten libc upgrades, it truncates files, it wrecks its own metadata.  I cannot recommend against it strongly enough.

ReiserFS: in the general case, this FS is okay.  However, recovering it from corruption can take literally hours, and it has a tiny fraction of the number of developers as ext3.

Since ext3 can grow while mounted, handles recovery well, and has tons of developers, I think it&#039;s the best choice unless you have really really specific needs.]]></description>
		<content:encoded><![CDATA[<p>I have to agree with most people here.</p>
<p>XFS: I have seen repeated, disastrous, corruptions with XFS.  It has eaten libc upgrades, it truncates files, it wrecks its own metadata.  I cannot recommend against it strongly enough.</p>
<p>ReiserFS: in the general case, this FS is okay.  However, recovering it from corruption can take literally hours, and it has a tiny fraction of the number of developers as ext3.</p>
<p>Since ext3 can grow while mounted, handles recovery well, and has tons of developers, I think it&#8217;s the best choice unless you have really really specific needs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jdong</title>
		<link>http://pthree.org/2008/04/23/xfs-vs-reiser/#comment-98763</link>
		<dc:creator>jdong</dc:creator>
		<pubDate>Wed, 23 Apr 2008 14:44:57 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=568#comment-98763</guid>
		<description><![CDATA[Err, when your reiser requires a fsck, good luck :) It&#039;s about the MOST sensitive fscker to random data on the disk and easily gets side-tracked and rebuilds a trash B-tree and calls it quits.


XFS is not designed to be a desktop filesystem where a good proportion of your files are small and constantly created/deleted. It is good for a storage partition for your multimedia content though -- possibly the best suited for the job.]]></description>
		<content:encoded><![CDATA[<p>Err, when your reiser requires a fsck, good luck <img src='http://pthree.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  It&#8217;s about the MOST sensitive fscker to random data on the disk and easily gets side-tracked and rebuilds a trash B-tree and calls it quits.</p>
<p>XFS is not designed to be a desktop filesystem where a good proportion of your files are small and constantly created/deleted. It is good for a storage partition for your multimedia content though &#8212; possibly the best suited for the job.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Travis</title>
		<link>http://pthree.org/2008/04/23/xfs-vs-reiser/#comment-98760</link>
		<dc:creator>Travis</dc:creator>
		<pubDate>Wed, 23 Apr 2008 14:36:30 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=568#comment-98760</guid>
		<description><![CDATA[Interesting Jeff.  In my experience, using reiser for several years, it is the best at recovering.  Actually, I&#039;ve found that it&#039;s better at recovering than xfs.  I built 2 machines with xfs and had multiple corruptions, especially with my firefox profile for some reason.  I&#039;ve never lost a byte to reiser.

XFS is not particularly suited for a desktop machine ... man it felt slow.

Reiser always feels fast.]]></description>
		<content:encoded><![CDATA[<p>Interesting Jeff.  In my experience, using reiser for several years, it is the best at recovering.  Actually, I&#8217;ve found that it&#8217;s better at recovering than xfs.  I built 2 machines with xfs and had multiple corruptions, especially with my firefox profile for some reason.  I&#8217;ve never lost a byte to reiser.</p>
<p>XFS is not particularly suited for a desktop machine &#8230; man it felt slow.</p>
<p>Reiser always feels fast.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Schroeder</title>
		<link>http://pthree.org/2008/04/23/xfs-vs-reiser/#comment-98752</link>
		<dc:creator>Jeff Schroeder</dc:creator>
		<pubDate>Wed, 23 Apr 2008 14:06:59 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=568#comment-98752</guid>
		<description><![CDATA[Not long ago, there was a guy on Linux kernel planet that blogged about creating a new filesystem. He did exhaustive benchmarks on the main Linux filesystems to see what he was up against. Here are some non-biased benchmarks for you to look at:

http://tservice.net.ru/~s0mbre/old/?section=projects&amp;item=fs_contest2

reiser3 and resier4 get pretty impressive results in a lot of areas. From experience, reiserfs is the WORST filesystem at recovering from hard shutdowns. It is more likely to corrupt itsself and require an fsck than any other filesystem.]]></description>
		<content:encoded><![CDATA[<p>Not long ago, there was a guy on Linux kernel planet that blogged about creating a new filesystem. He did exhaustive benchmarks on the main Linux filesystems to see what he was up against. Here are some non-biased benchmarks for you to look at:</p>
<p><a href="http://tservice.net.ru/~s0mbre/old/?section=projects&#038;item=fs_contest2" rel="nofollow">http://tservice.net.ru/~s0mbre/old/?section=projects&#038;item=fs_contest2</a></p>
<p>reiser3 and resier4 get pretty impressive results in a lot of areas. From experience, reiserfs is the WORST filesystem at recovering from hard shutdowns. It is more likely to corrupt itsself and require an fsck than any other filesystem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leandro Peracchi</title>
		<link>http://pthree.org/2008/04/23/xfs-vs-reiser/#comment-98751</link>
		<dc:creator>Leandro Peracchi</dc:creator>
		<pubDate>Wed, 23 Apr 2008 14:03:23 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=568#comment-98751</guid>
		<description><![CDATA[Hi!

I´m from Brazil.

I want to install Ubuntu on a computer with two identical hard drives using RAID1 and encrypted volumes.

In 7.10 there was a bug that doesn´t allow install this way.

I tried one build of 8.04 and appears to me that the same bug is still there...

Do you know something about this?

P.S.: sorry for my poor english...  ;)]]></description>
		<content:encoded><![CDATA[<p>Hi!</p>
<p>I´m from Brazil.</p>
<p>I want to install Ubuntu on a computer with two identical hard drives using RAID1 and encrypted volumes.</p>
<p>In 7.10 there was a bug that doesn´t allow install this way.</p>
<p>I tried one build of 8.04 and appears to me that the same bug is still there&#8230;</p>
<p>Do you know something about this?</p>
<p>P.S.: sorry for my poor english&#8230;  <img src='http://pthree.org/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jimcooncat</title>
		<link>http://pthree.org/2008/04/23/xfs-vs-reiser/#comment-98743</link>
		<dc:creator>jimcooncat</dc:creator>
		<pubDate>Wed, 23 Apr 2008 13:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=568#comment-98743</guid>
		<description><![CDATA[John (jdong): That is excellent info! Perhaps it&#039;s time for me to start reconsidering what I&#039;m doing.

Aaron: I&#039;ll be watching for your followup. Good luck!]]></description>
		<content:encoded><![CDATA[<p>John (jdong): That is excellent info! Perhaps it&#8217;s time for me to start reconsidering what I&#8217;m doing.</p>
<p>Aaron: I&#8217;ll be watching for your followup. Good luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jimcooncat</title>
		<link>http://pthree.org/2008/04/23/xfs-vs-reiser/#comment-98740</link>
		<dc:creator>jimcooncat</dc:creator>
		<pubDate>Wed, 23 Apr 2008 13:25:06 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=568#comment-98740</guid>
		<description><![CDATA[I&#039;ve been a ReiserFS fan for years, since building my first in-house mail server from Gentoo and Qmail, many years ago. A few tips on its use (the first for ANY filesystem):

Check your hard disk before committing your personal data to it. Run badblocks shortly after installation, and if there are any, consider trashing the disk. If you can afford the time to set it up, install smartmontools to use modern disks&#039; ability to warn you if the disk is going bad.

When mounting a partition that boots, (/ or a separate /boot partition), use the -notail option. This prevents small files from staying absorbed in the filesystem, which boot managers don&#039;t like. You can also use it for partitions you want maximum performance on at the expense of disk space. The old Gentoo docs used to specify a separate /boot partition because of this. That&#039;s too much to maintian for me. I use a / partition with -notail, but a separate /home without the option. Perhaps next time I&#039;ll use -notail on /home too, but my systems are working great for now.

Most filesystems (I don&#039;t know about XFS or other esoteric ones) bog down when approaching maximum capacity. I&#039;ve found (through observation only, no benchmarks) that somewhere between 90% and 95% full the disk screaming stops and my own screaming starts. I set a monitor (I use monit, but a quick cron/bash script would work well) to warn me at 80% full. Then it&#039;s time for me to start purging back to 60% or start planning to increase capacity. 

Note that we&#039;re NOT talking about Reiser4, we&#039;re talking about ReiserFS.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve been a ReiserFS fan for years, since building my first in-house mail server from Gentoo and Qmail, many years ago. A few tips on its use (the first for ANY filesystem):</p>
<p>Check your hard disk before committing your personal data to it. Run badblocks shortly after installation, and if there are any, consider trashing the disk. If you can afford the time to set it up, install smartmontools to use modern disks&#8217; ability to warn you if the disk is going bad.</p>
<p>When mounting a partition that boots, (/ or a separate /boot partition), use the -notail option. This prevents small files from staying absorbed in the filesystem, which boot managers don&#8217;t like. You can also use it for partitions you want maximum performance on at the expense of disk space. The old Gentoo docs used to specify a separate /boot partition because of this. That&#8217;s too much to maintian for me. I use a / partition with -notail, but a separate /home without the option. Perhaps next time I&#8217;ll use -notail on /home too, but my systems are working great for now.</p>
<p>Most filesystems (I don&#8217;t know about XFS or other esoteric ones) bog down when approaching maximum capacity. I&#8217;ve found (through observation only, no benchmarks) that somewhere between 90% and 95% full the disk screaming stops and my own screaming starts. I set a monitor (I use monit, but a quick cron/bash script would work well) to warn me at 80% full. Then it&#8217;s time for me to start purging back to 60% or start planning to increase capacity. </p>
<p>Note that we&#8217;re NOT talking about Reiser4, we&#8217;re talking about ReiserFS.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
