Anthony Campbell wrote:
>Or should I issue tune2fs commands
>(with appropriate time or mount switches) and change /etc/fstab in >some way?
>If so, how?
When you modify your /etc/fstab, you'll sacrifice either backward
compatibility to ext2 (if you change the fs type), or as Alan
mentions, the a
Alan Shutko wrote:
>You can replay the journal. That helps you if the filesystem is
>unclean because the system crashed. It doesn't help you _at all_ if
>the filesystem was silently corrupted because of a bad cable, or
>because the drive is going bad, or because of a bug in your kernel, or
>any
On 20 Nov 2001, Joerg Johannes wrote:
>
> > Any illumination gratefully received.
> >
> > Anthony
>
> Still waiting for it myself...
>
> joerg
>
Many thanks to yourself, Alan Shutko, and Miquel van Smoo for replies. I
am now quite a bit more illuminated.
Anthony
--
Anthony Campbell - runn
Paolo Falcone <[EMAIL PROTECTED]> writes:
>>> The second one is to tweak your ext3fs partition. issue:
>>>
>>> tune2fs -c0 -i0 /dev/hdb1
>>
>>Bad idea. From the tune2fs man page
> Well, I'm fully aware of that.
Apparently not.
> Generally, I'll agree that ommitting the fs checks is quite
Anthony Campbell wrote:
> It's precisely the above warnings that make me rather nervous of using
> ext3 (though I have it on all my filesystems at the moment, mainly to
> cope with the frequent lockups I am experiencing, for unknown reasons).
> The available documentation on ext3 doesn't seem to m
In article <[EMAIL PROTECTED]>,
Paolo Falcone <[EMAIL PROTECTED]> wrote:
>ok... I've done remounting root as read-only compared to deleting the
>journal. It's much easier to delete the .journal file (since you
>can have it reinstalled with the tune2fs command) but it's quite
Deleting the .journal
Anthony Campbell <[EMAIL PROTECTED]> writes:
> It's precisely the above warnings that make me rather nervous of using
> ext3
They shouldn't. Those warnings apply just as much to ext2, or xfs,
even reiserfs[1]. All it's saying is that unrelated kernel bugs,
drive failures, or other problems may
In article <[EMAIL PROTECTED]>,
Anthony Campbell <[EMAIL PROTECTED]> wrote:
>It's precisely the above warnings that make me rather nervous of using
>ext3 (though I have it on all my filesystems at the moment, mainly to
>cope with the frequent lockups I am experiencing, for unknown reasons).
>The a
Alan Shutko wrote:
>Paolo Falcone <[EMAIL PROTECTED]> writes:
>
>>>blaubaer:~# e2fsck /dev/hdb1
>>>e2fsck 1.25 (20-Sep-2001)
>>>/dev/hdb1 is mounted.
>>>WARNING!!! Running e2fsck on a mounted filesystem may cause
>>>SEVERE filesystem damage.
>>
>> This is default behavior. But you need to del
On 20 Nov 2001, Alan Shutko wrote:
> Paolo Falcone <[EMAIL PROTECTED]> writes:
>
> >>blaubaer:~# e2fsck /dev/hdb1
> >>e2fsck 1.25 (20-Sep-2001)
> >>/dev/hdb1 is mounted.
> >>WARNING!!! Running e2fsck on a mounted filesystem may cause
> >>SEVERE filesystem damage.
> >
> > This is default behavi
Paolo Falcone <[EMAIL PROTECTED]> writes:
>>blaubaer:~# e2fsck /dev/hdb1
>>e2fsck 1.25 (20-Sep-2001)
>>/dev/hdb1 is mounted.
>>WARNING!!! Running e2fsck on a mounted filesystem may cause
>>SEVERE filesystem damage.
>
> This is default behavior. But you need to delete the journal
> file first,
=?ISO-8859-1?Q?J=F6rg?= Johannes wrote:
>I have ext3fs on all partitions (except /boot, which is usualy >mounted ro).
>When the maximum mount count is reached, ext3 tells me "EXT3-fs >warning:
I guess your /etc/fstab looks somehow like this
//dev/hdb1ext2defaults,errors=remoun
Hello List
I have ext3fs on all partitions (except /boot, which is usualy mounted ro).
When the maximum mount count is reached, ext3 tells me "EXT3-fs warning:
maximal mount count reached, running e2fsck is recommended"
What is the easiest way to run e2fsck automatically on bootup, when the
max
13 matches
Mail list logo
