s-strickthrough
June 12th, 2019, 07:39 PM
First post!
I've setup my computer a few ways. First was simple with just Ubuntu 18.04, all of my data on the same partition as the OS and nautilus was quick everywhere.
My new system is dual boot with an ntfs shared partition. The pertinent points of my new setup are: Ubuntu 18.04 OS is on the root partition, my home folder is on an ext4 formatted partition (houses mostly the dot files), and my non-dot files are on the shared ntfs formatted partition. For instance, the ~/Documents folder is a symbolic link to the corresponding Documents folder on the shared partition whereas my .config folder is on the ext4 formatted home partition. My /etc/fstab file reads:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p4 during installation
UUID=fb46f379-2bfa-46dc-bb14-b31db42d5b2c / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=2A21-363D /boot/efi vfat umask=0077 0 1
# /home was on /dev/nvme0n1p5 during installation
UUID=c57d851b-fde7-436a-8b76-3705cfaac690 /home ext4 defaults 0 2
# /media/stephen/Lindows was on /dev/nvme0n1p6 New Addition
UUID=3AC0F7D6C0F795FB /media/stephen/Lindows ntfs defaults,umask=000,uid=1000,gid=1000 0 2
/swapfile none swap sw 0 0
The problem:
When I use nautilus to navigate this sea of partitions and links, its performance is wildly inconsistent, unlike the way it was before the multiple partitions and symbolic links (the contents of the folders before and after the system changes are the same).
To give an example, if I click the files icon on the launcher, the home directory it brings up is slow to navigate (up/down buttons and expanding/descending into a directory) AND the cpu usage for the nautilus command maxes out the core it runs on for about 20 seconds for each navigation operation. If instead, I go Other Locations -> Computer and then use the expandable folders, I can navigate (up down and expand a directory) in no time and with no cpu issues either (both folders on root and home and shared partitions). The problem then continues that if I descend (not expand) into a folder on the root partition, navigation is smooth, but descending into any folder on the home partition is immediately sluggish with the same preceding issues.
It may be a connected issue but nautilus-desktop does the same king of cpu usage for the first 20-ish seconds after booting.
To be clear, this isn't an access issue to the partition. I have used rsync to move 40G of data between the shared and home partitions in about 5 minutes.
Any help would be greatly appreciated!
I've setup my computer a few ways. First was simple with just Ubuntu 18.04, all of my data on the same partition as the OS and nautilus was quick everywhere.
My new system is dual boot with an ntfs shared partition. The pertinent points of my new setup are: Ubuntu 18.04 OS is on the root partition, my home folder is on an ext4 formatted partition (houses mostly the dot files), and my non-dot files are on the shared ntfs formatted partition. For instance, the ~/Documents folder is a symbolic link to the corresponding Documents folder on the shared partition whereas my .config folder is on the ext4 formatted home partition. My /etc/fstab file reads:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p4 during installation
UUID=fb46f379-2bfa-46dc-bb14-b31db42d5b2c / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=2A21-363D /boot/efi vfat umask=0077 0 1
# /home was on /dev/nvme0n1p5 during installation
UUID=c57d851b-fde7-436a-8b76-3705cfaac690 /home ext4 defaults 0 2
# /media/stephen/Lindows was on /dev/nvme0n1p6 New Addition
UUID=3AC0F7D6C0F795FB /media/stephen/Lindows ntfs defaults,umask=000,uid=1000,gid=1000 0 2
/swapfile none swap sw 0 0
The problem:
When I use nautilus to navigate this sea of partitions and links, its performance is wildly inconsistent, unlike the way it was before the multiple partitions and symbolic links (the contents of the folders before and after the system changes are the same).
To give an example, if I click the files icon on the launcher, the home directory it brings up is slow to navigate (up/down buttons and expanding/descending into a directory) AND the cpu usage for the nautilus command maxes out the core it runs on for about 20 seconds for each navigation operation. If instead, I go Other Locations -> Computer and then use the expandable folders, I can navigate (up down and expand a directory) in no time and with no cpu issues either (both folders on root and home and shared partitions). The problem then continues that if I descend (not expand) into a folder on the root partition, navigation is smooth, but descending into any folder on the home partition is immediately sluggish with the same preceding issues.
It may be a connected issue but nautilus-desktop does the same king of cpu usage for the first 20-ish seconds after booting.
To be clear, this isn't an access issue to the partition. I have used rsync to move 40G of data between the shared and home partitions in about 5 minutes.
Any help would be greatly appreciated!