Титла: Монтиране на NTFS дял в убунту 9.10
Публикувано от: Ipolit в Dec 27, 2009, 12:02
Имам 2 компютъра с Windows XP и Ubuntu 9.10. Забелязах, че като монтирам уиндоуски дял в Убунтуто и компютрите се забавят чувствително. Като пусна top, най-сериозния лоуд ми е от това монтиране. PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2428 root 20 0 2824 1108 592 R 43.4 0.2 1:33.88 mount.ntfs
1435 root 20 0 103m 19m 4208 S 3.3 4.0 4:41.16 Xorg
1529 ipolit 20 0 3232 1468 676 S 0.7 0.3 0:03.51 dbus-daemon
2602 ipolit 20 0 38044 13m 10m S 0.7 2.8 0:01.31 gnome-terminal
Това нормално ли е? И има ли някакви опции за по-безболезнено монтиране?
Титла: Re: Монтиране на NTFS дял в убунту 9.10
Публикувано от: vyrgozunqk в Dec 27, 2009, 13:50
Особено сваляш ли нещо или използваш ли активно NTFS-кият дял е нормално да ти заема много процесорно време Why does the driver have high CPU utilization?
The most common explanations are
Not using at least NTFS-3G Version 2009.3.8.
Writing multi-GB files on a highly internally fragmented volume.
Some software are using the most inefficient block sizes by default.
A highly sparse file is being regularly written or updated.
Some software indeed do intensive file operations sometimes (Beagle, Amarok collectionscanner, updatedb, Spotlight, etc).
The CPU usage is not directly visible in case of kernel file system drivers but this is not true for user space drivers. That is, they are in the process list unlike the kernel drivers. Higher CPU usage is normal and expected in some scenarios. This is true for most file systems, not only NTFS-3G.
The NTFS block size (cluster size) is smaller than 4096 bytes. This often happens, for instance, if FAT32 was converted to NTFS. The driver always logs this information for block devices. You can search for the value of the ‘blksize’ in the system log files under the /var/logs directory. Typically this information can be found in the ‘messages’ or ‘daemon.log’ log file, depending on your operating system.
Using an embedded device or a very fast I/O subsystem (100+ MB/s, RAID).
VMware is not using “mainMem.useNamedFile=FALSE” in the .vmx file.
Status: An optimized, high-performance version, primarily for consumer electronics devices, is available commercially. Ако искаш нещо в пъто ( 30 до 50 ) по-бързо виж това Тук ($2)
|