From: Steve Lord <lord@sgi.com>
To: Pavel Machek <pavel@suse.cz>
Cc: David Woodhouse <dwmw2@infradead.org>,
adam.keys@HOTARD.engr.smu.edu, linux-kernel@vger.kernel.org
Subject: Re: journaling and devel [was Re: Development Setups]
Date: Sat, 13 Oct 2001 15:30:06 -0500 [thread overview]
Message-ID: <200110132030.f9DKU6D02263@jen.americas.sgi.com> (raw)
In-Reply-To: Message from Pavel Machek <pavel@suse.cz> of "Sat, 06 Oct 2001 00:27:41 -0000." <20011006002741.A35@toy.ucw.cz>
>
> I disagree.. With journal filesystem, when something is silently corrupting
> your disk, you'll never know. With ext2, you sometimes sync & reset to make
> sure your disks are still healthy. I would not recommend journaling on
> experimental boxes.
> Pavel
On the otherhand I have found the main problem with using XFS on development
platforms is that you do not test the kernel shutdown code very much.
It is much faster to just reset the box than to do a shutdown, and it
does not make a difference when you bring it back up.
Steve
next prev parent reply other threads:[~2001-10-13 20:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-05 4:20 Development Setups Adam Keys
2001-10-05 4:36 ` Michael Rothwell
2001-10-05 8:02 ` David Woodhouse
2001-10-06 0:27 ` journaling and devel [was Re: Development Setups] Pavel Machek
2001-10-13 20:30 ` Steve Lord [this message]
2001-10-05 9:50 ` Development Setups Riley Williams
2001-10-05 11:22 ` Alan Cox
2001-10-05 14:53 ` Jeff Dike
2001-10-05 17:15 ` Andrew Ebling
2001-10-06 11:38 ` Adrian Cox
2001-10-13 20:38 ` Tim Moore
2001-10-15 9:09 journaling and devel [was Re: Development Setups] Andreas Dilger
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=200110132030.f9DKU6D02263@jen.americas.sgi.com \
--to=lord@sgi.com \
--cc=adam.keys@HOTARD.engr.smu.edu \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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®