On 07/02/2012 11:06 AM, Jean-Pierre André wrote:
> 
> 
> Jean-Pierre André wrote:
>> Hi,
>>
>> g4hx wrote:
>>> On 07/01/2012 10:40 PM, Jean-Pierre André wrote:
>>>
>>> g4hx wrote:
>>>>> Hello everyone,
>>>>>
>>>>> I much appreciate your work on the ntfs-3g driver, I think that
>>>>> ntfs is
>>>>> the only file system that can be used on linux and windows together.
>>>>> However, there seems to be a performance problem with the ntfs-3g
>>>>> driver:
>>>>> I get write rates of about 3 mb/s as opposed to about 90 mb/s with
>>>>> different file system types on the same disk. Also I have a very high
>>>>> CPU load, caused by the mount.ntfs process.
>>>>
>>>
>>> Hello Jean-Pierre,
>>>
>>> first of all, thanks for the fast reply, I am very impressed. Also I did
>>> not mean to imply that you guys are not doing your very best to help
>>> improve ntfs-3g.
>>>
>>> I attached the files that you wanted to see. During the mount with the
>>> debug-* programs I of course also ran dd to produce some relevant data.
>>>
>>> You may also notice that this particular ntfs partition is inside of a
>>> truecrypt container. This does not seem to be the issue as the same
>>> happens on partitions which are not encrypted. Also I think it unlikely
>>> that the issue is related to fragmentation since the problem also occurs
>>> with another partition which should be relatively clean
>>
>> Your data show a very unusual pattern : more than
>> half the time is spent locating attributes. You only
>> opened four files (probably a single one four times),
>> so you must have a file with a lot of attributes such
>> as names (hard links) or extended attributes.
>>
>> Can you say more on what you were doing, and
>> post the output of "ntfsinfo -fvi inode device"
>> where inode is the inode number of your unusual
>> file (which you can get from "ls -li filename").
>> This is likely to be long, as there are about 30
>> extents to the inode.
> 
> Can you also please post the output of
> "ntfsinfo -fvi 0 device" ?
> 
>> Regards
>>
>> Jean-Pierre
>>
> 

Hi,

well, essentially I mounted the file system and used "dd oflags=append
conv=notrunc if=/dev/zeros of=./zeroes" to measure the write speed. I
also mounted the partition with "-odebug,nodetach" and got a lot of
these messages during the writing:

WRITE[0] 512 bytes to 124918424064
   WRITE[0] 512 bytes
   unique: 28611, error: 0 (Success), outsize: 24
unique: 28612, opcode: GETXATTR (22), nodeid: 11, insize: 68
   unique: 28612, error: -61 (No data available), outsize: 16
unique: 28613, opcode: WRITE (16), nodeid: 11, insize: 576

I attached the inode information of the files "./zeroes" and inode 0.
The file has already grown to a size of about 117G, which is why I think
the output is so large.

I mainly use this partition to store mp3s and avis, so after copying the
files I did not do much with the partition except reading from it, so I
don't think that there should be a fragmentation problem.

edit: I pasted the inode information of "./zeroes" here:
http://pastebin.com/Jrk1Nbzz



g4hx



Dumping Inode 0 (0x0)
Upd. Seq. Array Off.:    48 (0x30)
Upd. Seq. Array Count:   3 (0x3)
Upd. Seq. Number:        14907 (0x3a3b)
LogFile Seq. Number:     0x0
MFT Record Seq. Numb.:   1 (0x1)
Number of Hard Links:    1 (0x1)
Attribute Offset:        56 (0x38)
MFT Record Flags:        IN_USE 
Bytes Used:              416 (0x1a0) bytes
Bytes Allocated:         1024 (0x400) bytes
Next Attribute Instance: 4 (0x4)
MFT Padding:    00 00 
Dumping attribute $STANDARD_INFORMATION (0x10) from mft record 0 (0x0)
        Attribute length:        96 (0x60)
        Resident:                Yes
        Name length:             0 (0x0)
        Name offset:             24 (0x18)
        Attribute flags:         0x0000
        Attribute instance:      0 (0x0)
        Data size:               72 (0x48)
        Data offset:             24 (0x18)
        Resident flags:          0x00
        ReservedR:               0 (0x0)
        File Creation Time:      Mon Jan  1 00:00:00 1601 UTC
        File Altered Time:       Mon Jan  1 00:00:00 1601 UTC
        MFT Changed Time:        Mon Jan  1 00:00:00 1601 UTC
        Last Accessed Time:      Mon Jan  1 00:00:00 1601 UTC
        File attributes:         HIDDEN SYSTEM (0x00000000)
        Maximum versions:        0 
        Version number:          0 
        Class ID:                0 
        User ID:                 0 (0x0)
        Security ID:             0 (0x0)
        Quota charged:           0 (0x0)
        Update Sequence Number:  0 (0x0)
Dumping attribute $FILE_NAME (0x30) from mft record 0 (0x0)
        Attribute length:        104 (0x68)
        Resident:                Yes
        Name length:             0 (0x0)
        Name offset:             24 (0x18)
        Attribute flags:         0x0000
        Attribute instance:      2 (0x2)
        Data size:               74 (0x4a)
        Data offset:             24 (0x18)
        Resident flags:          0x01
        ReservedR:               0 (0x0)
        Parent directory:        5 (0x5)
        File Creation Time:      Thu Feb 23 07:28:35 2012 UTC
        File Altered Time:       Thu Feb 23 07:28:35 2012 UTC
        MFT Changed Time:        Thu Feb 23 07:28:35 2012 UTC
        Last Accessed Time:      Thu Feb 23 07:28:35 2012 UTC
        Allocated Size:          28672 (0x7000)
        Data Size:               27648 (0x6c00)
        Filename Length:         4 (0x4)
        File attributes:         HIDDEN SYSTEM (0x00000000)
        Namespace:               Win32 & DOS
        Filename:                '$MFT'
Dumping attribute $DATA (0x80) from mft record 0 (0x0)
        Attribute length:        80 (0x50)
        Resident:                No
        Name length:             0 (0x0)
        Name offset:             64 (0x40)
        Attribute flags:         0x0000
        Attribute instance:      1 (0x1)
        Lowest VCN               0 (0x0)
        Highest VCN:             52894 (0xce9e)
        Mapping pairs offset:    64 (0x40)
        Compression unit:        0 (0x0)
        Data size:               216657920 (0xce9f000)
        Allocated size:          216657920 (0xce9f000)
        Initialized size:        216657920 (0xce9f000)
        Runlist:        VCN             LCN             Length
                        0x0             0x4             0x4003
                        0x4003          0x5008          0x8e9c
Dumping attribute $BITMAP (0xb0) from mft record 0 (0x0)
        Attribute length:        72 (0x48)
        Resident:                No
        Name length:             0 (0x0)
        Name offset:             64 (0x40)
        Attribute flags:         0x0000
        Attribute instance:      3 (0x3)
        Lowest VCN               0 (0x0)
        Highest VCN:             6 (0x6)
        Mapping pairs offset:    64 (0x40)
        Compression unit:        0 (0x0)
        Data size:               26448 (0x6750)
        Allocated size:          28672 (0x7000)
        Initialized size:        26448 (0x6750)
        Runlist:        VCN             LCN             Length
                        0x0             0x2             0x2
                        0x2             0x4007          0x5
End of inode reached
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
ntfs-3g-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel

Reply via email to