After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 629845 - Nautilus takes very long time to open large folders in ntfs external HD, Esata connected (file scan before access?)
Nautilus takes very long time to open large folders in ntfs external HD, Esat...
Status: RESOLVED DUPLICATE of bug 356836
Product: nautilus
Classification: Core
Component: Navigation
2.30.x
Other Linux
: Normal major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-09-16 13:00 UTC by Joël Obrecht
Modified: 2012-09-15 16:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Joël Obrecht 2010-09-16 13:00:32 UTC
I'm using archlinux, latest updates, Nautilus 2.30.1. I have an external HD (5400 RPM, 1TO) formatted in ntfs, and connected via eSata. It is mounted via the command "mount.ntfs" from the ntfs-3g pack. Since other software are working perfectly, I guess it is NOT a ntfs-3g problem, or it is a nautilus-related ntfs-3g problem.

When I open the mounted folder, or any other huge folder in the disk, for instance music (thousands of folders and files), Nautilus does not open them, instead it seems to perform a scan (the disk activity heard), which is very long (quite 2-3 minutes), and blocks all other operations. Once the "scan" is finished, I can open the folder and perform navigation, but I still have to wait decreasing times for every folder I have to explore.

This problem occurs even with smaller directories (50-150 MO of content) : I click on these directory, I hear the disk working some 2-10 seconds, then I have to reclick once to open.

I do not have this problem in simple windows to search for a file, for instance to open in an application (is it nautilus ?), and Pcmanfm work perfectly.

I've try to run a ntfs repair, but all is fine on this disk. I didn't have this problem on the beginning, even if I had huge files, but since some time (I do not remember exactly when) or some total filesize issue? According to gparted, I have 516 GO used on the disk, so lot of empty room is still there.

So I set the severity to major, because external HD are very important today, and I use that one for my work, and it is very painful. In windows (run in virtualbox), no access time problem either.
Comment 1 William Jon McCann 2012-09-15 16:38:21 UTC

*** This bug has been marked as a duplicate of bug 356836 ***