On Sun, Apr 30, 2000 at 11:43:34PM -0500, David Talkington wrote:
>
> Would passing the "read-only" option to the kernel at the LILO: prompt
> have the desired effect?
Actually I am a little worried about some disk errors I have gotten,
and am trying to be able to do this on a regular basis without having
to reboot everytime. At least, until I find out what is causing the
fscking disk errors:
Apr 30 04:24:43 localhost kernel: EXT2-fs warning (device ide0(3,4)):
ext2_free_blocks: bit already cleared for block 811296
Apr 30 04:24:43 localhost kernel: EXT2-fs warning (device ide0(3,4)):
ext2_free_inode: bit already cleared for inode 191782
Apr 30 04:24:43 localhost kernel: EXT2-fs warning (device ide0(3,4)):
ext2_free_blocks: bit already cleared for block 811291
Apr 30 04:24:43 localhost kernel: EXT2-fs warning (device ide0(3,4)):
ext2_free_inode: bit already cleared for inode 191777
> :On Sun, 30 Apr 2000, Hal Burgiss wrote:
> :> Trying to fsck my root partition on a running system, and I am now
> :> consistently getting:
> :>
> :> #init 1
> :> (appears to go alright ... )
> :> #umount -a
> :> mount: / device busy
> :>
> :> (or similar). Trying
> :>
> :> #mount -n -o remount,ro /
> :>
> :> also fails with same error. What is keeping this busy? Extremely few
> :> processes were running (less than 10?). This *should* work, no?
> :> Also, I occasionally get various FS as busy on shutdown. Right now I
> :> just want to run e2fsck, but after a zillion tries, I give up.
> :>
> :> Redhat 6.2 (with updates), kernel 2.2.15pre9 SMP. / is on IDE0, if that
> :> makes a difference. I've had the devices busy problem on shutdown with
> :> various kernels going back at least several months. Sometimes it
> :> works, sometimes it doesn't. Right now, it won't :( Any clues?
--
Hal B
[EMAIL PROTECTED]
--
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
