On Mon, Jan 20, 2003 at 09:11:12AM -0800, Steve Lamb wrote:
> On Mon, 20 Jan 2003 16:48:35 +
> Colin Watson <[EMAIL PROTECTED]> wrote:
> > That doesn't match either /etc/rcS.d/S30checkfs.sh or the e2fsck man
> > page.
>
> But it does match what man shutdown says.
Right, but I don't think
On Mon, 20 Jan 2003 16:48:35 +
Colin Watson <[EMAIL PROTECTED]> wrote:
> That doesn't match either /etc/rcS.d/S30checkfs.sh or the e2fsck man
> page.
But it does match what man shutdown says.
--
Steve C. Lamb | I'm your priest, I'm your shrink, I'm your
ICQ: 510
On Mon, Jan 20, 2003 at 07:45:34AM -0800, Paul Johnson wrote:
> On Mon, Jan 20, 2003 at 01:32:48PM +, Colin Watson wrote:
> > Won't the normal fsck on boot do the job? /forcefsck adds the -f option,
> > "force checking even if the file system seems clean"; I didn't realize
> > the forced check
On Mon, Jan 20, 2003 at 01:32:48PM +, Colin Watson wrote:
> Won't the normal fsck on boot do the job? /forcefsck adds the -f option,
> "force checking even if the file system seems clean"; I didn't realize
> the forced check was required here.
No, -f is fast boot, no filesystem check even if i
On Mon, Jan 20, 2003 at 07:49:18AM -0500, Michael P. Soulier wrote:
> On 20/01/03 John Griffiths did speaketh:
> > great, thanks.
> >
> > the forcefsck was recommended to me i didn't think it'd hurt.
>
> It was a good recommendation actually. The next fsck is what hides the
> journal permanen
On Mon, 20 Jan 2003 07:49:18 -0500
"Michael P. Soulier" <[EMAIL PROTECTED]> wrote:
> It was a good recommendation actually. The next fsck is what hides the
> journal permanently.
That it does. Personally I did it with shutdown -r -F. I recommend not
doing it from remote or without a con
On 20/01/03 John Griffiths did speaketh:
> great, thanks.
>
> the forcefsck was recommended to me i didn't think it'd hurt.
It was a good recommendation actually. The next fsck is what hides the
journal permanently.
Mike
--
Michael P. Soulier <[EMAIL PROTECTED]>, GnuPG pub key: 5BC8B
>
>You don't need to redo the tune2fs -j commands. You already have journals;
>they're just not being used yet. Just edit /etc/fstab and reboot.
>
>I don't know why you're doing the touch/forcefsck. I don't think it's
>necessary.
>
great, thanks.
the forcefsck was recommended to me i didn't think
On Mon, Jan 20, 2003 at 05:07:57PM +1100, John Griffiths wrote:
> so could i skip re-running the tune?
Yup.
--
.''`. Baloo <[EMAIL PROTECTED]>
: :' :proud Debian admin and user
`. `'`
`- Debian - when you have better things to do than to fix a system
msg25066/pgp0.pgp
Descrip
John Griffiths wrote:
> Whoops,
>
> missed a step converting a box to ext3
>
> procedure i was using was:
>
> 1) #tune2fs -j /dev/hda*
>
> for all ext2 file systems.
>
> 2) edit /etc/fstab to change all references from ext2 to auto
>
> 3) #touch/forcefsck
>
> 4) reboot
>
> only i forgot st
>
>Nope. ext3 is ext2 with a journal, basically. You might need to
>compile ext3 in, or have the module loaded from initrd.
>
so could i skip re-running the tune?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
>what does #touch/forcefsck do anyway ?
>
oops, should have read #touch /forcefsck
as i understand it forces an fsck on the reboot which sets the jounal up
properly
WARNING -
This email is confidential and may contain copyright material.
If you are not the intended recipient of Capital Moni
On Mon, Jan 20, 2003 at 04:34:47PM +1100, John Griffiths wrote:
> it rebooted fine and #cat /proc/mounts shows the / file ssystem as ext 2
> and the others as ext2
>
> i was thinking of just re-runnign the procedure and rebooting.
>
> is there any danger in this?
Nope. ext3 is ext2 with a journ
>
>
> Whoops,
>
> missed a step converting a box to ext3
>
> procedure i was using was:
>
> 1) #tune2fs -j /dev/hda*
>
> for all ext2 file systems.
>
> 2) edit /etc/fstab to change all references from ext2 to auto
>
> 3) #touch/forcefsck
>
> 4) reboot
>
> only i forgot step 2
>
> it reb
14 matches
Mail list logo
