mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sven-Haegar Koch <haegar@sdinet.de>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.19: File system corruption "stuck" until device is replugged
Date: Fri, 22 Dec 2006 14:16:08 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0612221410300.21828@mercury.sdinet.de> (raw)
In-Reply-To: <200612220759.11961.arvidjaar@mail.ru>

On Fri, 22 Dec 2006, Andrey Borzenkov wrote:

> I had USB stick (fat32) that reported file system corruption on mount and
> hence was mounted read-only. No amount of umount/dosfsck/mount could make it
> rw again. dosfsck reported device as clean but it still would mount ro and I
> continued to see directory that had been deleted by the very first dosfsck
> run! I unplugged it, looked under Win2k - it was OK - and only then did I
> notice that directory claimed as corrupted did not even exist. Replugging
> it - mounted OK.
>
> I am not sure if this is a bug or "work as designed". May be this is specific
> fat32 problem; still it does not look right?

I think at the first mount time there was a read error for an unknown 
reason, and this turned the partition (not the filesystem) into read-only 
mode. All further mount attempts only found a read-only medium, and thus 
where only able to mount read-only. I've been bitten by this more than 
once, too - there seems to be no way to avoid a reboot/replug when one of 
your data disks has thrown a read error, taking (for me) the whole server 
down, when just one unimportant data-disk thinks it has problems again (as 
happens with my home-server about once every one or two weeks).

c'ya
sven

-- 

The Internet treats censorship as a routing problem, and routes around it.
(John Gilmore on http://www.cygnus.com/~gnu/)

      reply	other threads:[~2006-12-22 13:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-22  4:59 Andrey Borzenkov
2006-12-22 13:16 ` Sven-Haegar Koch [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=Pine.LNX.4.64.0612221410300.21828@mercury.sdinet.de \
    --to=haegar@sdinet.de \
    --cc=arvidjaar@mail.ru \
    --cc=linux-kernel@vger.kernel.org \
    /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®