On Thu, 10 Jun 1999, Raider wrote:
> Richard Adams wrote:
> > Try reading 'man rm'.
> > Quite possably what you need is;
> > 'rm -- -filename'
> > Files or directorys beginning with special chars, cannot be deleted
even by
> > root with just 'rm - '
>
> It's very strage. I mean take a look. This is part of the
fist
> page of the output:
> total 833165668
> srwx----w- 1 13869 8736 892155456 Jan 9 1987 #61186=
> cr----Sr-- 1 11651 9510 59, 145 Sep 4 1971 #61187
> b-wx--S--t 1 5441 39578 154, 149 Apr 22 2024 #61189
> c---r-SrwT 1 7963 9766 55, 116 Jun 18 2036 #61196
This is obviously a y2k problem :-) ^^^^^^^^
>
> For me it doesn't make any sense. And it's getting worse in
the
> listing. There are some files that are reported as soft links and
inside
> isn't stored the path to the real file but parts of files from my
> filesystem. Ok. So like showing parts of /var/logs/messages isn't
such a
> big problem because I'm the only one using this machine. But how come
> there are parts of messages I received? My $HOME is located on another
> partition.
> Else, does anybody has any solution? I have a very busy
period.
> And time is one thing I really lack. And it's getting more and more
> disturbing. So all works well. Than I shutdown the system.
Eventually I
> go to windoze to finnish some work. Next time I boot the root
filesystem
> is corrupted, sometimes beyond repair. These last days I reinstalled
> linux like it was windoze. I repeat: isn't from the hardware, unless
the
> 2.0.30 kernel is too stupid to work with a udma hard drive, but I don't
> think so.
> I love Linux, and I will miss a lot of features. But if I
don't
> find a solution I'll erase Linux - probably for good. It's somehow
> insulting. I mean I have OSR2 as well, and it didn't crash in about 3
> months. I'm desperate! And this is taking me too much time.
> My partition table looks like that:
> /dev/hda1 vfat 300M
> /dev/hda2 ext2 / 300M
> /dev/hda3 dos extended which contains 2 disks 2g each
> /dev/hda4 extended
> /dev/hda5 ext2 /usr 1g
> /dev/hda6 swap 24m
> /dev/hda7 ext2 /home 1g
> /dev/hda8 ext2 /extra the rest till 8.4g
>
> _No_other_partition_had_any_problems_so_far_. And had2 doesn't
> have any problems while I'm running it. The nightmare starts after
> shutdown (or at boot time).
>
> Raider
> --
> ``Liberate tu-temet ex inferis''
>
Last time something like this happened to me, the DMA on the motherboard
failed soon after (done anything with floppies, lately? See if they
still work) and I had to build this junk-pentium 66. I am still using
the same hd, though.
If you're _sure_ it's not hardware, the pattern of damage is not
inconsistent with the fs being written on by some other OS. Fat fs's
don't give a rat's ass what size the partition is. The size of the fs
is determined by entries in the partition boot record, and if that is
inconsistent with the partition size, they may well write all over some
other partition, starting with the adjacent one. dosfsck might catch
this, at least it seems to report files and clusters out of range, but
to be really sure I would use bpe on /dev/hda1 and see what is in byte
0xd (sectors per cluster), 0x16-17 (fat sectors), and 0x20-23 (sectors),
remebmbering that they are little-endian short and long ints (least
significan byte first). Fat sectors counts both fats, so divide it by
2, multiply it by 256, then by the sectors per cluster, and that is how
many sectors windows thinks it has to write on, not counting the FAT and
boot sector.
I hope this is some help to you.
Lawson
>< Microsoft free environment
This mail client runs on Wine. Your mileage may vary.
___________________________________________________________________
Get the Internet just the way you want it.
Free software, free e-mail, and free Internet access for a month!
Try Juno Web: http://dl.www.juno.com/dynoget/tagj.
