ext3_free_blocks_sb when removing a more than 1GB file

[Eric Sandeen]

On 3/4/11 11:33 AM, Stephane Cerveau wrote:
> Hello,
> 
> 
> I checked the storage that seems to be ok ( check bad block) and I
> still have the problem. I did the test on vfat and I don’t have the
> problem. I'm using a 2.6.23 kernel ? When the ext3 fs is considered
> as stable ?

I don't mean that it's an IO error or a bad block, but perhaps a behavioral
problem with the flash; maybe not syncing properly before it's powered
off, etc.  If it only happens with some USB drives, I do not think
it is an ext3 issue.

Your original problem report may not have been totally clear so maybe
I misunderstand.

Can you show exactly what you did, and exactly what error messages
you received, keeping in mind that any IO type errors that don't
say "ext3" are also relevant?

-Eric

> BR
> 
> -----Original Message----- From: Eric Sandeen
> [mailto:sandeen at redhat.com] Sent: vendredi 4 mars 2011 17:26 To:
> Stephane Cerveau Cc: ext3-users at redhat.com; Tristan Pateloup Subject:
> Re: ext3_free_blocks_sb when removing a more than 1GB file
> 
> On 3/4/11 9:45 AM, Stephane Cerveau wrote:
>> Dear all,
>> 
>> It seems that if I change the size of blocks to 2048 by mkfs.ext3
>> –b 2048 /dev/sda1, the problem does not appear.
>> 
>> Is there a way to know by advance what is the best block size for
>> an external device ?
>> 
>> BR
> 
> Sounds like a storage problem; not a filesystem problem, something to
> do with the flash behaving badly.
> 
> -Eric
> 
> 
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 5925 (20110304) __________
> 
> The message was checked by ESET NOD32 Antivirus.
> 
> http://www.eset.com
> 
> 
> 
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 5926 (20110304) __________
> 
> The message was checked by ESET NOD32 Antivirus.
> 
> http://www.eset.com
>