On Sunday 15 Jun 2003 3:13 am, Brian Parish wrote:
On Sun, 2003-06-15 at 11:49, JoeHill wrote:
WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.
Do you really want to continue (y/n)? no
OK, the easiest way to handle this is to boot from the first
On Sun, 15 Jun 2003 08:22:55 -0500
Tom Brinkman [EMAIL PROTECTED] uttered:
Did you rip to wav's or mp3's? I've never had any luck
normalizing anything but wav's. I get segfaults and corrupt mp3's
trying to normalize them ... just part way thru ;
rip to wav. I didn't know normalize would
On Sun, 15 Jun 2003 11:10:15 +0100
Richard Urwin [EMAIL PROTECTED] uttered:
The correct way is to drop to single user mode with telinit 1.
Then unmount /home if it is still mounted read-write.
That would have avoided a reboot? In any case, would it have allowed me
to simply delete or otherwise
On Sunday 15 Jun 2003 2:39 pm, JoeHill wrote:
On Sun, 15 Jun 2003 11:10:15 +0100
Richard Urwin [EMAIL PROTECTED] uttered:
The correct way is to drop to single user mode with telinit 1.
Then unmount /home if it is still mounted read-write.
That would have avoided a reboot?
Yes. It would
On Sun, 2003-06-15 at 09:25, JoeHill wrote:
Hi all,
I ripped some cd tracks to make a cd for a friend chris.
I ran normalize -m * in the dir ~/mp3/chris, and it segfaulted part
of the way through.
Now, if I try to even list the contents of the dir, the shell freezes,
ctrl-c will not
On Saturday 14 June 2003 07:25 pm, JoeHill wrote:
Any way out of this? I just want to delete the dir and start over. I
cannot even delete the parent dir!
Any help appreciated, as always.
First thing I would do is boot up with wither the rescue cd or something like
knoppix and run fsck on
On 15 Jun 2003 10:16:29 +1000
Brian Parish [EMAIL PROTECTED] uttered:
Sounds like the file system is corrupt. Have you tried fsck on this
partition?
everything else is fine. only that directory is screwed. I am not
familiar with fsck, but from the man page it seems to be a big stick for
a
On Sun, 2003-06-15 at 10:37, JoeHill wrote:
On 15 Jun 2003 10:16:29 +1000
Brian Parish [EMAIL PROTECTED] uttered:
Sounds like the file system is corrupt. Have you tried fsck on this
partition?
everything else is fine. only that directory is screwed. I am not
familiar with fsck, but
On 15 Jun 2003 10:55:46 +1000
Stephen Kuhn [EMAIL PROTECTED] uttered:
Have you tried to rename that directory, or move the contents of that
directory elsewhere, then delete the directory, then recreate the
directory and move all the old contents back into it?
I can rename the dir, but I
On 15 Jun 2003 10:16:29 +1000
Brian Parish [EMAIL PROTECTED] uttered:
Sounds like the file system is corrupt. Have you tried fsck on this
partition?
hmmm, this does not sound encouraging:
fsck 1.32 (09-Nov-2002)
e2fsck 1.32 (09-Nov-2002)
/dev/hda6 is mounted.
WARNING!!! Running e2fsck on
On Saturday 14 June 2003 08:46 pm, JoeHill wrote:
On 15 Jun 2003 10:55:46 +1000
Stephen Kuhn [EMAIL PROTECTED] uttered:
Have you tried to rename that directory, or move the contents of that
directory elsewhere, then delete the directory, then recreate the
directory and move all the old
On Saturday 14 June 2003 08:49 pm, JoeHill wrote:
On 15 Jun 2003 10:16:29 +1000
Brian Parish [EMAIL PROTECTED] uttered:
Sounds like the file system is corrupt. Have you tried fsck on this
partition?
hmmm, this does not sound encouraging:
fsck 1.32 (09-Nov-2002)
e2fsck 1.32
On Sun, 2003-06-15 at 11:49, JoeHill wrote:
On 15 Jun 2003 10:16:29 +1000
Brian Parish [EMAIL PROTECTED] uttered:
Sounds like the file system is corrupt. Have you tried fsck on this
partition?
hmmm, this does not sound encouraging:
fsck 1.32 (09-Nov-2002)
e2fsck 1.32 (09-Nov-2002)
On Sat, 14 Jun 2003 21:05:33 -0500, Dennis Myers
[EMAIL PROTECTED] wrote:
On Saturday 14 June 2003 08:46 pm, JoeHill wrote:
On 15 Jun 2003 10:55:46 +1000
Stephen Kuhn [EMAIL PROTECTED] uttered:
Have you tried to rename that directory, or move the contents of that
directory elsewhere, then
On 15 Jun 2003 12:13:19 +1000
Brian Parish [EMAIL PROTECTED] uttered:
WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.
Ah, so this is the problem is that fsck is dangerous when run on an
active filesystem.
OK, the easiest way to handle this is to
On Sat, 14 Jun 2003 19:25:51 -0400
JoeHill [EMAIL PROTECTED] uttered:
Well, fsck fsck!
All I had to do was reboot...
damn! I had a good one goin there... 11 days, no problems and then
something like normalize brings me down...and from the CLI no less!
Oh well, start again :(
Thanks for all
16 matches
Mail list logo
