mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolinux.com>
To: Wade Hampton <whampton@staffnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: apparent file corruption on 2.4.2
Date: Fri, 2 Mar 2001 14:05:15 -0700 (MST)	[thread overview]
Message-ID: <200103022105.f22L5FY16844@webber.adilger.net> (raw)
In-Reply-To: <3AA001DC.C11B688D@staffnet.com> from Wade Hampton at "Mar 2, 2001 03:26:04 pm"

Wade Hampton writes:
> I can't move, delete, or do anything with these files.  I tried 
> chattr, touch, etc. and the only thing I can do is change the 
> access date with touch.
> 
> b--sr-s--t    1 1769209956 1852796526 116, 101 May 29  2023
>               /binold/hostname
> 
> prwxr-x--T    1 2232483836 2312881283        0 Mar  1 22:41 
>               /dev/dsp
> 
> Does anyone have any ideas.  I can live with one messed up file 
> in /binold, but I can't live with a messed up /dev/dsp.  I 
> really don't want the Microsoft solution (reload)....

You could always rename /dev to /devold, copy the rest of your
device files back, and run "mknod /dev/dsp c 14 3" to recreate
/dev/dsp.

You probably need to boot using a rescue floppy (tomsrtbt if
needed), and run debugfs to delete them.  It is strange
that you can't even delete these files.  Sometimes there is a
problem with files > 2GB in size, but there should be no
problems with block special or pipes.  What sort of errors do
you get, and is there anything in syslog?

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert

      reply	other threads:[~2001-03-02 21:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-02 20:26 Wade Hampton
2001-03-02 21:05 ` Andreas Dilger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200103022105.f22L5FY16844@webber.adilger.net \
    --to=adilger@turbolinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=whampton@staffnet.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®