public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carlos Rodrigues <carlos.efr@mail.telepac.pt>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: Horms <horms@debian.org>,
	308072@bugs.debian.org, linux-kernel@vger.kernel.org
Subject: Re: statfs returns wrong values for 250Gb FAT fs
Date: Tue, 10 May 2005 21:34:46 +0100	[thread overview]
Message-ID: <42811AE6.7020902@mail.telepac.pt> (raw)
In-Reply-To: <87oebjxpcc.fsf@devron.myhome.or.jp>

OGAWA Hirofumi wrote:

>Filesystem may have the corrupted free-cluster value.
>
>I couldn't reproduce the problem on 2.6.12-rc4.
>
>Could you try a recently dosfsck (dosfstools-2.11 or later)?
>Also could you send the output of above program?
>  
>

"dosfsck" did find a problem in the free-cluster value. And also said 
the backups FAT was different than the original FAT.

I didn't use "dosfsck" to fix the problems though (not that it couldn't, 
I just didn't try). As I had already copied everything to another disk, 
I just used "mkdosfs" to reformat the drive, and it works just fine now.

I still don't know what caused this, probably something related to some 
"kernel panics" I was seeing on shutdown (in a Fedora 3 installation, 
not Debian), after doing an umount+unplug.

I didn't though of using "dosfsck" because Windows' checkdisk was saying 
the filesystem was perfectly fine... It makes me feel really safe 
trusting MS tools... not.

Carlos Rodrigues


  reply	other threads:[~2005-05-10 20:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1DUT2T-0000fm-Nx@localhost.localdomain>
2005-05-10  8:09 ` statfs returns wrong values for 250Gb FAT fs Horms
2005-05-10 12:00   ` OGAWA Hirofumi
2005-05-10 20:34     ` Carlos Rodrigues [this message]
2005-05-11 12:23       ` Paul Ionescu
2005-05-12 20:32         ` OGAWA Hirofumi

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=42811AE6.7020902@mail.telepac.pt \
    --to=carlos.efr@mail.telepac.pt \
    --cc=308072@bugs.debian.org \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=horms@debian.org \
    --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