linux-kernel - Re: Is there a way to limit VFAT allocation?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <453485E9.7010502@dunaweb.hu>
Date:	Tue, 17 Oct 2006 09:27:37 +0200
From:	Zoltan Boszormenyi <zboszor@...aweb.hu>
To:	Rene Scharfe <rene.scharfe@...fire.ath.cx>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Is there a way to limit VFAT allocation?

Rene Scharfe írta:
> Zoltan Boszormenyi schrieb:
>   
>> Prakash Punnoor írta:
>>     
>>> Am Montag 16 Oktober 2006 12:06 schrieb Zoltan Boszormenyi:
>>>  
>>>       
>>>> Is there a way to tell the VFAT driver to exclude
>>>> the last N sectors from the allocation strategy?
>>>>     
>>>>         
>>> Can't you mark that clusters as bad with a diskeditor?
>>>   
>>>       
>> Can you suggest one that works on Linux?
>> Or which bits should I change if I use LDE?
>> (lde.sourceforge.net)
>>     
>
> Try mbadblocks, part of the Mtools package (http://mtools.linux.lu/).
> If it doesn't help, and you are brave, you may want to play with
> mdoctorfat, which comes with Mtools, too, but is hidden for some reason. :->
>
> René
>   

Thanks. I have set up my /root/.mtoolsrc and:

# mbadblocks x:
plain_io: Input/output error
Bad cluster 63985 found
plain_io: Input/output error
Bad cluster 63986 found
plain_io: Input/output error
Bad cluster 63987 found
plain_io: Input/output error
Bad cluster 63988 found
plain_io: Input/output error
Bad cluster 63989 found

After unplugging the device didn't reformat itself.
Filling the disk seems to be working. It gives me
"disk full" without any new "Buffer I/O error on device sdc1"
or FAT panic messages in the kernel logs.

Thanks and best regards,
Zoltán Böszörményi

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/