From: Grzegorz Kulewski <kangur@polcom.net>
To: Zoltan Boszormenyi <zboszor@dunaweb.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is there a way to limit VFAT allocation?
Date: Mon, 16 Oct 2006 12:37:48 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.63.0610161233400.14187@alpha.polcom.net> (raw)
In-Reply-To: <4533598A.3040909@dunaweb.hu>
Hi,
On Mon, 16 Oct 2006, Zoltan Boszormenyi wrote:
> I have bought a 2GB MP3 player / flash disk
> that erroneously partitions and formats its storage.
> The built-in firmware has an off-by-one bug that
> creates the partition one cylinder larger that the
> disk size allows and then it formats the VFAT fs
> according to the buggy partition size. No wonder
> when I try to copy large amounts of data to the
> flash disk it detects errors and then remounts it
> read-only.
>
> I tried to repartition and reformat it three times
> with different mformat or mkdosfs options
> but as soon as I remove it from the USB port,
> the device detects changed disk format and
> automatically reformats itself again, so it
> stays buggy.
[snip]
> Unfortunately, the firmware is not upgradeable.
> The device in question is a Telstar UFM-102B.
>
> Is there a way to tell the VFAT driver to exclude
> the last N sectors from the allocation strategy?
Maybe try to setup device mapper linear mapping backed by portion of that
partition that is ok (== one cylinder smaller) instead of messing with
filesystem drivers. And then create filesystem on top of that new device.
Grzegorz Kulewski
prev parent reply other threads:[~2006-10-16 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 10:06 Zoltan Boszormenyi
2006-10-16 10:25 ` Prakash Punnoor
2006-10-16 10:57 ` Zoltan Boszormenyi
2006-10-16 17:10 ` Rene Scharfe
2006-10-17 7:27 ` Zoltan Boszormenyi
2006-10-16 10:37 ` Grzegorz Kulewski [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.63.0610161233400.14187@alpha.polcom.net \
--to=kangur@polcom.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zboszor@dunaweb.hu \
/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®