From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-kernel@vger.kernel.org
Subject: 2.6.19: File system corruption "stuck" until device is replugged
Date: Fri, 22 Dec 2006 07:59:05 +0300 [thread overview]
Message-ID: <200612220759.11961.arvidjaar@mail.ru> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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?
TIA
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFi2YfR6LMutpd94wRAquCAKC3n8DjRGRqDYdfP6tNGvlg5sG0MQCfQRNJ
89HQuNaAWuLzJkkKayVrLks=
=m0rH
-----END PGP SIGNATURE-----
next reply other threads:[~2006-12-22 6:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-22 4:59 Andrey Borzenkov [this message]
2006-12-22 13:16 ` 2.6.19: File system corruption "stuck" until device is replugged Sven-Haegar Koch
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=200612220759.11961.arvidjaar@mail.ru \
--to=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