Re: Howto manually trigger fsck

2002-01-20 Thread Devon
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 20 January 2002 12:46 pm, john-paul delaney wrote: > I tried the shutdown being the safer (read easier) of the two, the > filesystem checked out ok. Therefore I'm left with a full root > directory but not knowing what's occupying all that

Re: Howto manually trigger fsck

2002-01-20 Thread john-paul delaney
Yes! That was the question to show me what an idiot I am... I had moved the files mentioned - instead of to a newly partitioned disk /dev/hdc3, to a directory (created by mistake) on the root called hd3. Sorry to have wasted your time gentlemen - but you saved me from making more fatal mistake

Re: Howto manually trigger fsck

2002-01-20 Thread Bret Hughes
On Sun, 2002-01-20 at 11:46, john-paul delaney wrote: > Thanks, I appreciate your help... > > I tried the shutdown being the safer (read easier) of the two, the filesystem > checked out ok. Therefore I'm left with a full root directory but not knowing > what's occupying all that space. > >

Re: Howto manually trigger fsck

2002-01-20 Thread Nick Wilson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * On 20-01-02 at 15:45 * john-paul delaney said > Thanks, I appreciate your help... > > I tried the shutdown being the safer (read easier) of the two, the filesystem > checked out ok. Therefore I'm left with a full root directory but not kno

Re: Howto manually trigger fsck

2002-01-20 Thread john-paul delaney
Thanks, I appreciate your help... I tried the shutdown being the safer (read easier) of the two, the filesystem checked out ok. Therefore I'm left with a full root directory but not knowing what's occupying all that space. I had moved off some directories but still there's no improvement (mc

Re: Howto manually trigger fsck

2002-01-20 Thread Nick Wilson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I think 'shutdown -rF now' might help. * On 20-01-02 at 14:33 * Duncan Hill said > On Sun, 20 Jan 2002, john-paul delaney wrote: > > > "Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage.." > > > > Things are bad enough

Re: Howto manually trigger fsck

2002-01-20 Thread Duncan Hill
On Sun, 20 Jan 2002, john-paul delaney wrote: > "Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage.." > > Things are bad enough as it is, so I abort the command. > However I would like to trigger a manual filesystem check... how can I do so? man tune2fs -- Sapere aude

Howto manually trigger fsck

2002-01-20 Thread john-paul delaney
Hello List... fsck /dev/hda1 output warns: "Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage.." Things are bad enough as it is, so I abort the command. However I would like to trigger a manual filesystem check... how can I do so? thanks /j-p. JU