Date: Mon, 19 Dec 2005 19:32:11 -0500 From: "Brandon S. Allbery KF8NH" <allbery@ece.cmu.edu> To: petre@kgb.ro Cc: freebsd-current@freebsd.org Subject: Re: "Native" journaling file systems? Message-ID: <E47CD3DB-71A4-464E-8CCC-F0492BF0A4A1@ece.cmu.edu> In-Reply-To: <1263.193.231.237.171.1135037978.squirrel@dummy-host.example.com> References: <1263.193.231.237.171.1135037978.squirrel@dummy-host.example.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 19, 2005, at 7:19 , petre@kgb.ro wrote: >> On 2005-12-19 10:28, Justin Smith <jsmith@drexel.edu> wrote: >> I've used several journaling file systems in Linux and like the >> Reiser >> FS except for one MAJOR drawback: When something goes wrong, >> reiser-fsck >> absolutely sucks at repairing things (Hans Reiser freely admits >> that but >> says it's never needed because nothing ever goes wrong). > > hmmm, reiserfsck --rebuild-tree solved my problems twice; or was it > pure > luck ? ;) There are versions of reiserfs that are fairly stable (many of them in SuSE Linux releases, with a boatload of patches to make them stable) --- but I don't like what I've been hearing and seeing with the new version, and we've scrapped it in our production Linux environment in favor of ext3 (temporarily) and xfs (in progress). (No production FreeBSD: we absolutely *need* AFS clients, and none of us is enough of a kernel-level hacker to make OpenAFS or Arla sufficiently stable. *grumble*) -- brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E47CD3DB-71A4-464E-8CCC-F0492BF0A4A1>