Re: [PATCH] bug fix for ntfs

["Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2332 bytes --]

On 23.04.2012 17:26, Bean wrote:
> Hi,
>
> 2012/4/23 Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com>:
>> On 23.04.2012 16:41, Bean wrote:
>>> Hi all,
>>>
>>> This patch fix three issues:
>>>
>>> 1, In ntfsdoc, it says namespace = 0 means POSIX and it's case
>>> sensitive. However, i found out this is not sure in Windows 7 as some
>>> system directory use this value as well. Now i ignore this flag and
>>> treat all files in ntfs as case insensitive.
>> This would be wrong. It's certаinly possible to create files differing
>> only in case in POSIX namespace, so it's case-sensitive. If some system
>> directory uses this namespace it's case-sensitive
> Do you know any tool that can create case sensitive file in ntfs ?
> ntfsdoc is not official so it can get it wrong, or MS may change the
> meaning of some flags. At least I can't create file in different case
> as those directories so this should mean it's case insensitive.
Have you tried with ntfs-3g?
Also if the problem is with only one directory, it's better if it stays
the way it is. The only quirk associated with false assumption about
case-sensitivity is the need to reference the name in correct case which
should be done anyway. If you wrongly assume case insensitivity some
files may become inaccessible with is more serious.
OS may forbid some file names without it being FS limitation (conversely
OS may fail to enforce FS limitation like an old trick with ".." in the
root directory)

>>> 2, Previous version doesn't return blocklist information for small
>>> files embed in MFT, this patch fixes it. For example, create a
>>> 512-byte file test in ntfs and try this command:
>>>
>>> grub-fstest /ntfs.img blocklist /test
>> It looks like this part of patch has issues. Like that it doesn't handle
>> the case when the read is split across 2 sectors or if MFT entry is at
>> offset >=1024. Or that it adds some checks (like "invalid mft offset")
>> which weren't there previously and which would make GRUB bail out on
>> weird FS even if user doesn't want blocklists.
> MFT in ntfs is only 1024 bytes, and it must be sector aligned, so if
> this test fails, there is serious problem with the fs (or the driver).
Is it true for 4K sector NTFS?

-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]