9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Harri Haataja <harriha@mail.student.oulu.fi>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Plan9 installation invading the other partitions?
Date: Mon, 24 Jul 2006 03:22:34 +0300	[thread overview]
Message-ID: <20060724002234.GE1836@XTL.antioffline.net> (raw)
In-Reply-To: <45219fb00607210451l6cfba555w6a764d30fe4415eb@mail.gmail.com>

On Fri, Jul 21, 2006 at 01:51:44PM +0200, Lluís Batlle wrote:
> 2006/7/21, Christian Walther <cptsalek@gmail.com>:
> >I wouldn't blame Plan 9 for damaging another partition it shouldn't
> >even touch. I'd blame ReiserFS. I heard several stories from friends
> >and collegues who used ReiserFS about file system corruption. You
> >might want to use your favorite search engine, but from my point of
> >view ReiserFS isn't stable enough for everydays use.
> >The alternatives are either called ext3 or jfs, I suppose. XFS is
> >nice, too, but it tends to corrupt the file system in case of a
> >sudden system crash (e.g. after power fail), especially on heavy
> >loaded file systems.
> Yes, I heard that also about ReiserFS. But practically, I've lost
> files using ext3 (I used it for some months). Too many, so I stopped
> using it. I've never lost files using ReiserFS (since years of usage)
> until this week - and only two tmp files were lost. About XFS, which I
> used for a year or so, had namely the problem of sudden system crash.
> The filesystem didn't get corrupted, but simply some files (mostly
> important ones) were blank after reboot.

I've taken damage on reiserfs and found out that there wasn't really
much anything in a way of recovery tools or diagnostics. About
everything anything managed to say that the fs is dead. XFS is still the
only system that I've had nearly guaranteed data loss (and not much sign
of when or where until you find the blank files) if anything goes wrong
with a fs in use. Never on Irix, though. There it always worked
flawlessly despite equal randomness in power status and hardware faults
etc.
At the moment (well, that means the last few years; installations aren't
that frequent) I'm sticking to ext3 on any Linux hosts I may be looking
after.

-- 
"What do you mean? A handgun is a standard tool for a sysadmin, isn't it?"
		-- Kurt M. Hockenbury, Scary Devil Monastery


  parent reply	other threads:[~2006-07-24  0:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-19 20:53 Lluís Batlle i Rossell
2006-07-20  5:14 ` Russ Cox
2006-07-21 11:09   ` Lluís Batlle
2006-07-21 11:43 ` Christian Walther
2006-07-21 11:51   ` Lluís Batlle
2006-07-21 14:22     ` Iruatã Souza (muzgo)
2006-07-24  0:22     ` Harri Haataja [this message]
2006-07-24  0:28       ` erik quanstrom
2006-07-24 13:46       ` Paweł Lasek

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=20060724002234.GE1836@XTL.antioffline.net \
    --to=harriha@mail.student.oulu.fi \
    --cc=9fans@cse.psu.edu \
    /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).