From: Petter Larsen <pla@morecom.no>
To: Eugene Crosser <crosser@rol.ru>
Cc: ext3 <ext3-users@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: mode data=journal in ext3. Is it safe to use?
Date: Thu, 17 Jun 2004 10:36:53 +0200 [thread overview]
Message-ID: <1087461413.2765.42.camel@pla.lokal.lan> (raw)
In-Reply-To: <1087323602.16701.42.camel@ariel.sovam.com>
> >
> > Data integrity is much more important for us than speed.
>
> I ran ext3 with data=journal on 2.6.6smp for about a week on a heavily
> loaded system (I mean it). I did not ever experience filesystem
> corruption (related to the fs code). I did, however, hit complete
> system lockup once. It *may* have been unrelated to the fs code.
>
> (If you use quota, it *will* lock. The author is working on a fix.
> Above, I am referring to a lockup with quota off).
>
> Eugene
Good to here. But there may have been a lookup once because you are not
sure that the crash was unrelated to ext3 fs code?
Are you going to test it more?
We are not going to use quota, we are using ext3 on a compact flash disk
in an embedded device.
--
Petter Larsen
cand. scient.
moreCom as
913 17 222
next prev parent reply other threads:[~2004-06-17 8:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <40FB8221D224C44393B0549DDB7A5CE83E31B1@tor.lokal.lan>
2004-06-15 18:09 ` Petter Larsen
2004-06-15 18:20 ` Eugene Crosser
2004-06-17 8:36 ` Petter Larsen [this message]
2004-06-16 7:34 ` Oleg Drokin
2004-06-17 8:27 ` Petter Larsen
2004-06-17 17:09 ` Oleg Drokin
2004-06-18 9:41 ` Helge Hafting
2004-06-18 10:15 ` Oleg Drokin
2004-06-18 11:30 ` Paulo Marques
2004-06-18 12:05 ` Oleg Drokin
2004-06-21 17:42 ` mode data=journal in ext3. Is it safe to use? Conclusion Petter Larsen
2004-06-19 19:16 ` mode data=journal in ext3. Is it safe to use? Bernd Eckenfels
2004-06-16 15:49 ` Timothy Miller
2004-06-17 0:51 ` Daniel Pittman
2004-06-17 3:02 ` Tim Connors
2004-06-17 5:35 ` Hans Reiser
2004-06-17 10:08 ` Dave Jones
2004-06-17 16:55 ` Hans Reiser
2004-06-17 8:29 ` Petter Larsen
2004-06-17 19:30 ` Daniel Egger
[not found] ` <87wu26mto2.fsf@enki.rimspace.net>
2004-06-27 14:17 ` Petter Larsen
2004-06-28 0:22 ` Daniel Pittman
[not found] ` <1805.216.148.213.196.1087426691.squirrel@www.code-visions.com>
2004-06-17 11:23 ` Petter Larsen
2004-06-17 16:26 ` Andreas Dilger
2004-06-17 14:56 Ken Ryan
2004-06-17 16:06 ` Timothy Miller
2004-06-17 17:20 ` Hans Reiser
2004-06-17 19:15 ` Ken Ryan
2004-06-18 6:18 ` Hans Reiser
2004-06-17 19:43 ` Daniel Egger
2004-06-17 19:59 ` Ken Ryan
2004-06-19 14:49 ` Petter Larsen
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=1087461413.2765.42.camel@pla.lokal.lan \
--to=pla@morecom.no \
--cc=crosser@rol.ru \
--cc=ext3-users@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®