From: Dirk Schenkewitz <Dirk.Schenkewitz@interface-ag.com>
To: Reiserfs List <reiserfs-list@namesys.com>
Subject: Re: Corrupted/unreadable journal: reiser vs. ext3
Date: Mon, 17 Feb 2003 11:04:08 +0100 [thread overview]
Message-ID: <3E50B398.306B0AC7@interface-ag.com> (raw)
Sorry for being that late, I didn't see it on first view.
Sam Vilain wrote:
> On Wed, 12 Feb 2003 08:43, berthiaume_wayne@emc.com wrote:
> > Dirk, I'd be interested in hearing from you your performance
> > experience with ext3 when it reaches 96% full.
>
> No problem, because you get ENOSPC at 95% or 90%.
Not at my system - I have (for example) a 16 Gig partition with
ext3 on it which is 100% full and has now 6100 kilobytes free space.
No Problem (with getting ENOSPC, I mean :-)).
Oh - wait a sec: do you usually reserve 5%-10% for the superuser?
That might explain why you get ENOSPC at 95%-90%, because that
reserved space is not taken into account... I normally tune the
fs to reserve 0% for the superuser. I never needed the reserved
space anyway.
> Hmm, another feature SysAdmins actually find useful, missing in
> reiserfs.
> Along with quotas (this feature is a lazy case of a quota, really).
>
> On Wed, 12 Feb 2003 18:12, Ross Vandegrift wrote:
> > You have to start your software on some kind of foundation.
> > Working hardware sounds like a great place to me.
>
> Hmm, you've never heard of redundancy or fault tolerance then.
>
> What part fails the most in running systems ? Disk platters.
>
> CPUs might overheat and RAM might suddenly one day get a sticky bit,
Even then I'd like the OS to find out about that and inform me...
> but as you point out there ain't much you can do about it.
> Except buy a Tandem, or use ECC memory.
>
> But with disks, you can. Mirroring aside, modern hard disks use S.M.A.R.T.
> technology which claims to be able to spot failures before they happen.
> Many BIOSes will let you turn this feature on and off. Of course I've
> never actually seen it in action :-).
For me the most important thing is: if something is vital to a fs,
it must be protected even against hardware failure as good as possible.
For example, by making copies, or (perhaps) at least having reserved
space for a copy, and if some access fails, mark the blocks as bad,
give a warning (important) and start using the reserved space.
Have fun
dirk
--
Dirk Schenkewitz
InterFace AG fon: +49 (0)89 / 610 49 - 126
Leipziger Str. 16 fax: +49 (0)89 / 610 49 - 83
D-82008 Unterhaching
http://www.interface-ag.de mailto:dirk.schenkewitz@interface-ag.de
next reply other threads:[~2003-02-17 10:04 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 10:04 Dirk Schenkewitz [this message]
2003-02-20 1:27 ` Corrupted/unreadable journal: reiser vs. ext3 Juan Quintela
2003-02-20 9:03 ` Anders Widman
2003-02-23 20:35 ` cheap quota systems (was: Re: Corrupted/unreadable journal: reiser vs. ext3) Zygo Blaxell
-- strict thread matches above, loose matches on Subject: below --
2003-02-20 9:55 Corrupted/unreadable journal: reiser vs. ext3 Dirk Schenkewitz
2003-02-20 10:20 ` Anders Widman
2003-02-14 14:30 Dirk Schenkewitz
2003-02-14 14:20 Dirk Schenkewitz
2003-02-14 20:58 ` Valdis.Kletnieks
2003-02-14 0:18 Sam Vilain
2003-02-23 23:31 ` Zygo Blaxell
2003-02-24 1:14 ` Anders Widman
2003-02-14 0:17 Sam Vilain
2003-02-14 0:16 Sam Vilain
2003-02-23 23:10 ` Zygo Blaxell
2003-02-12 20:57 Dirk Schenkewitz
2003-02-12 20:05 Dirk Schenkewitz
2003-02-13 22:49 ` Zygo Blaxell
2003-02-14 0:32 ` Hans Reiser
2003-02-14 8:18 ` Oleg Drokin
2003-02-14 10:13 ` Andreas Dilger
2003-02-14 10:17 ` Oleg Drokin
2003-02-14 10:50 ` Andreas Dilger
2003-02-14 10:59 ` Oleg Drokin
2003-02-14 13:34 ` Hans Reiser
2003-02-14 16:04 ` Rudy Zijlstra
2003-02-14 19:06 ` Andreas Dilger
2003-02-14 19:19 ` Hans Reiser
2003-02-15 12:51 ` Vitaly Fertman
2003-02-15 13:00 ` Vitaly Fertman
2003-02-18 19:50 ` Hans Reiser
2003-02-18 20:05 ` Vitaly Fertman
2003-02-18 22:18 ` Hans Reiser
2003-02-15 13:04 ` Anders Widman
2003-02-15 13:23 ` Oleg Drokin
2003-02-17 19:43 ` Hans Reiser
2003-02-15 22:37 ` Andreas Dilger
2003-02-18 18:21 ` Hans Reiser
2003-02-18 19:22 ` Oleg Drokin
2003-02-18 19:28 ` Hans Reiser
2003-02-18 21:17 ` Valdis.Kletnieks
2003-02-18 22:02 ` Matthias Andree
2003-02-19 6:26 ` Oleg Drokin
2003-02-18 22:23 ` Hans Reiser
2003-02-12 18:27 Anders Widman
2003-02-11 19:43 berthiaume_wayne
2003-02-12 10:48 ` Dirk Schenkewitz
2003-02-12 10:59 ` Hans Reiser
2003-02-12 11:24 ` Frank Baumgart
2003-02-12 11:35 ` Stefan Traby
2003-02-12 11:54 ` Dirk Schenkewitz
2003-02-12 12:42 ` Hans Reiser
2003-02-12 13:25 ` Dirk Schenkewitz
2003-02-12 16:22 ` Sam Vilain
2003-02-12 16:53 ` Anders Widman
2003-02-12 17:19 ` Hans Reiser
2003-02-12 17:40 ` Anders Widman
2003-02-12 18:15 ` Dirk Mueller
2003-02-12 18:20 ` Anders Widman
2003-02-12 18:20 ` Chris Dukes
2003-02-13 20:08 ` Zygo Blaxell
2003-02-11 18:59 Dirk Schenkewitz
2003-02-11 20:27 ` Hans Reiser
2003-02-11 21:30 ` Mike Hodson
2003-02-11 21:47 ` Hans Reiser
2003-02-11 21:58 ` Hans Reiser
2003-02-12 6:35 ` Oleg Drokin
2003-02-11 23:11 ` Adam Goryachev
2003-02-11 23:17 ` Anders Widman
2003-02-12 0:12 ` Hans Reiser
2003-02-12 10:23 ` Anders Widman
2003-02-12 10:47 ` Hans Reiser
2003-02-12 11:12 ` Adam Goryachev
2003-02-12 13:42 ` Anders Widman
2003-02-12 14:15 ` Russell Coker
2003-02-12 15:26 ` Anders Widman
2003-02-12 16:22 ` bscott
2003-02-12 16:28 ` Russell Coker
2003-02-12 16:40 ` Anders Widman
2003-02-13 3:42 ` Zygo Blaxell
2003-02-13 10:13 ` Anders Widman
2003-02-13 14:44 ` Rudy Zijlstra
2003-02-13 3:31 ` Zygo Blaxell
2003-02-12 16:39 ` Sam Vilain
2003-02-12 5:12 ` Ross Vandegrift
2003-02-12 7:17 ` Oleg Drokin
2003-02-12 10:17 ` Alexander Lyamin
2003-02-12 10:19 ` Alexander Lyamin
2003-02-12 16:25 ` Vitaly Fertman
2003-02-12 16:56 ` Anders Widman
2003-02-12 17:13 ` Oleg Drokin
2003-02-12 1:02 ` Mike Hodson
2003-02-12 7:25 ` Oleg Drokin
2003-02-12 9:45 ` Hans Reiser
2003-02-12 16:09 ` Sam Vilain
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=3E50B398.306B0AC7@interface-ag.com \
--to=dirk.schenkewitz@interface-ag.com \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.