I remember back in '99 when Paul Sack wrote:
> I forgot what the subject name was of the whole fsck thread. Anyways, I
> got the same problem as the person who initially had a problem. (dumped
> into a shell to fix it.) I didn't have a problem fixing it with fsck.
> I'm really glad I read the thread. Thanks everyone! Anyways, it happened
> after I copied a large number of mp3's (300mb or so) from my windows
> partition to my linux partition. Person who originally posted: Did you
> do anything similar? Could this possibly be an error with linux vfat
> implementation???

Generally, the only time when I have problems with this sort of thing
is when the system catestrophically crashes (power failuer, mighty
kernel panic, &c.)  The drive usually[1] isn't fsck'd unless it
was not unmounted cleanly last time it was mounted.

> While I'm at it: I was having some wierd lpd problems and someone
> offered some suggestions but I have a really wierd problem now- lpd
> doesn't print any errors to the console but I looked in the logs (in
> /var/logs/messages, specifically) and lpd reports: No device lp1.
> (Something very similar to that. ) lp1 is in /dev. And it is okay,
> afaik. I didn't mess with anything there. Should I recompile lpd??

Did you upgrade to 2.2?  lp1 in 2.0 and less is now lp0.

                Matt

[1] Every once in a while a fsck is forced, just to make sure no
errors creep into the fs.  I think it's a prameter you can set
with tunefs

-- 
/* Matt Sayler -- [EMAIL PROTECTED] -- atwork?astronomy:cs
   http://www.cs.utexas.edu/users/mpsayler   -- (512)471-7450
   Have you ever imagined a world with no hypothetical situations? */
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]

Reply via email to