public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: DervishD <lkml@dervishd.net>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Wrong free clusters count on FAT32
Date: Thu, 19 Apr 2007 16:23:29 +0200	[thread overview]
Message-ID: <20070419142329.GG8287@DervishD> (raw)
In-Reply-To: <46274407.8010602@panasas.com>

    Hi Boaz :)

 * Boaz Harrosh <bharrosh@panasas.com> dixit:
> > Apart from not using the device itself to delete files (and probably
> > not using Windows for that, either) and to run fsck.vfat now and
> > then, is anything I can do to avoid this problem?
> > 
> Not that I know how to fix it. But have you tried running chkdsk on a
> device deleted files in windows. Just that I know, that windows would
> silently ignore fat errors and will only report them in chkdsk.

    I've done that and the problem is not fixed. I have to use fsck.vfat
instead.

> Deleting files in windows works fine. There is no problems with it and
> windows updates everything. I do that all the time.

    True, I've tested it, too. I'm going to report the problem to the
device manufacturer (it's a Cowon iAUDIO), but probably doing it in the
device will be very slow :(

> (I would even theorize that if you delete files on the device and than
> farther delete more files on windows, than windows will fix the
> problem on the fly)

    Probably, and it may be a good fix, but I seldom plug the device on
Windows.

    Thanks for the answer :)

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!

  reply	other threads:[~2007-04-19 14:21 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-19  8:57 Wrong free clusters count on FAT32 DervishD
2007-04-19 10:27 ` Boaz Harrosh
2007-04-19 14:23   ` DervishD [this message]
2007-04-19 11:52 ` Juergen Beisert
2007-04-19 14:19   ` DervishD
2007-04-21 22:42     ` OGAWA Hirofumi
2007-04-22  3:18       ` Andrew Morton
2007-04-22  4:26         ` OGAWA Hirofumi
2007-04-22 11:26           ` DervishD
2007-04-22 11:55             ` OGAWA Hirofumi
2007-04-22 20:08               ` DervishD
2007-04-23  2:27                 ` OGAWA Hirofumi
2007-04-23  6:19                   ` DervishD
2007-04-22 11:17       ` DervishD
2007-04-22 11:28       ` Juergen Beisert
     [not found] <8bAF0-3Yj-29@gated-at.bofh.it>
     [not found] ` <8bDta-8rc-31@gated-at.bofh.it>
     [not found]   ` <8bFEr-3B4-1@gated-at.bofh.it>
     [not found]     ` <8cwz8-2fE-13@gated-at.bofh.it>
2007-04-22 13:28       ` Bodo Eggert
2007-04-22 14:04         ` OGAWA Hirofumi
2007-04-22 14:29           ` OGAWA Hirofumi
2007-04-22 14:53             ` Andreas Schwab
2007-04-22 15:13               ` OGAWA Hirofumi
2007-04-22 21:46           ` Bodo Eggert
2007-04-23  2:20             ` OGAWA Hirofumi
2007-04-22 20:11         ` DervishD
     [not found]       ` <8cAMl-du-3@gated-at.bofh.it>
     [not found]         ` <8cBS7-1Qa-1@gated-at.bofh.it>
     [not found]           ` <8cIqE-3qZ-9@gated-at.bofh.it>
     [not found]             ` <8cITG-40H-5@gated-at.bofh.it>
2007-04-22 17:21               ` Bodo Eggert
2007-04-22 17:44                 ` 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=20070419142329.GG8287@DervishD \
    --to=lkml@dervishd.net \
    --cc=bharrosh@panasas.com \
    --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