Hi,
On Wed, 8 Dec 1999 17:28:49 -0500, "Theodore Y. Ts'o" <[EMAIL PROTECTED]>
said:
> Never fear, there will be an very easy way to switch back and forth
> between ext2 and ext3. A single mount command, or at most a single
> tune2fs command, should be all that it takes, no matter how the
> jour
Date: Mon, 6 Dec 1999 22:52:18 +0100
From: Pavel Machek <[EMAIL PROTECTED]>
> No, and I'm pretty much convinced now that I'll move to having a
> private, hidden inode for the journal in the future.
Please don't do that. Current way of switching ext2/ext3 is very
nice. If some
In message <[EMAIL PROTECTED]>, Pavel Machek writes:
> Hi!
>
> > No, and I'm pretty much convinced now that I'll move to having a
> > private, hidden inode for the journal in the future.
>
> Please don't do that. Current way of switching ext2/ext3 is very
> nice. If someone wants to shoot in the
Hi!
> No, and I'm pretty much convinced now that I'll move to having a
> private, hidden inode for the journal in the future.
Please don't do that. Current way of switching ext2/ext3 is very
nice. If someone wants to shoot in their foot...
Hi,
On Sat, 4 Dec 1999 12:11:58 -0700, mike burrell <[EMAIL PROTECTED]> said:
> couldn't you just make a new flag for the inode that journal.dat uses? i'm
> guessing using S_IMMUTABLE will cause some problems, but something similar
> to that?
The immutable flag will work fine: journaling bypas
Hi,
On Sat, 4 Dec 1999 08:44:46 -0800 (PST), Brion Vibber
<[EMAIL PROTECTED]> said:
> Maybe at least stick a nice big warning in the docs along the lines of
> "do not write to your journal file while mounted with journaling on,
> you big dummy!" :) Not that I'd do so deliberately of course, but
On Sat, 4 Dec 1999, mike burrell wrote:
> couldn't you just make a new flag for the inode that journal.dat uses? i'm
> guessing using S_IMMUTABLE will cause some problems, but something similar
> to that?
I gate immutable a try on a loopbacked test fs and it seems to work
fine... No complaints
Mr. James W. Laferriere ([EMAIL PROTECTED]) said:
> Hello All, Not being ext3/journaling savy , I ask this question
> Does journal.dat belong in user file area ? Could it not be put
> into (a little harder to overwrite) /proc ? Or ... ? Hth, JimL
you have to keep it associat
Hello All, Not being ext3/journaling savy , I ask this question
Does journal.dat belong in user file area ? Could it not be put
into (a little harder to overwrite) /proc ? Or ... ? Hth, JimL
On Sat, 4 Dec 1999, Brion Vibber wrote:
> On Sat, 4 Dec 1999, Daniel Veillard
On Sat, 4 Dec 1999, Daniel Veillard wrote:
> Let me guess, did your copy command avoided overwriting the journal.dat ?
> If not it's not surprizing, that's the only way (with soft raid + ext3)
> I found to get an oops from ext3.
(Sound of head banging against wall... ouch!) Yep, that would d
> However while copying my /home partition prior to repartitioning a drive,
> I got an oops in the journaling code... I had just created a new ~2GB ext2
> partition on hda5 (4k blocks, volume label set, otherwise default options)
> using mke2fs 1.18, created a blank 8192000 byte journal.dat file o
I'm running Linux 2.2.13 SMP with Jens Axboe's CD-ROM patch and
ext3-0.0.2c (with KDB patch applied but not activated) and have been using
journaling on my / and /home partitions for about a week and a half,
saving me a good hour or two in fsck times after Quake3-related crashes.
:)
However whil
12 matches
Mail list logo
