Try the async option. This should not be an issue for a local file system but we had huge latency issues on a nfs share with sync set.
The fstab entry should look like: UUID=129403c9-1c93-4391-be12-8c529a6656e9 / ext4 async,noatime,errors=remount-ro 0 1 Glenn Glenn L. Hickman Jr. Sr. RF Engineer WHRO 5200 Hampton Boulevard | Norfolk, VA 23508 P: 757.575.5064 | F: 757.489.0007 [email protected] whro.org ________________________________ From: [email protected] [[email protected]] on behalf of Pedro Picoto [[email protected]] Sent: Wednesday, February 19, 2014 17:44 To: Karl Koscher Cc: [email protected] Subject: Re: [RDD] Too long to save VTs I just edited the file on gedit under root. mount / -o remount,noatime... no improvement... On Wed, Feb 19, 2014 at 10:29 PM, Karl Koscher <[email protected]<mailto:[email protected]>> wrote: Have you rebooted and/or remounted the root file system? You can try it instantly without rebooting by doing: mount / -o remount,noatime On Wed, Feb 19, 2014 at 2:10 PM, Pedro Picoto <[email protected]<mailto:[email protected]>> wrote: Looking like this now: # /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> proc /proc proc noatime,nodev,noexec,nosuid 0 0 # / was on /dev/sda1 during installation UUID=129403c9-1c93-4391-be12-8c529a6656e9 / ext4 noatime,errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=c70ea169-fd8f-4e0f-aa55-f3a5d9a9c100 none swap sw 0 0 Still having troubles. CPU goes from 25% to 80% while RDLogedit performs VT operations, taking about 1' to Save and 1.30' to Do Over... On Wed, Feb 19, 2014 at 9:54 PM, Karl Koscher <[email protected]<mailto:[email protected]>> wrote: Just to be clear: it should look like this after: UUID=129403c9-1c93-4391-be12-8c529a6656e9 / ext4 noatime,errors=remount-ro 0 1 On Wed, Feb 19, 2014 at 1:09 PM, Cowboy <[email protected]<mailto:[email protected]>> wrote: On Wednesday 19 February 2014 03:53:13 pm Pedro Picoto wrote: > Here's why I have on the Fstab file: > > # /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> > proc /proc proc nodev,noexec,nosuid 0 0 > # / was on /dev/sda1 during installation > UUID=129403c9-1c93-4391-be12-8c529a6656e9 / ext4 > errors=remount-ro 0 1 > # swap was on /dev/sda5 during installation > UUID=c70ea169-fd8f-4e0f-aa55-f3a5d9a9c100 none swap > sw 0 0 > > Where should I place the noatime flag? > In the options column. -- Cowboy http://cowboy.cwf1.com Feel disillusioned? I've got some great new illusions ... _______________________________________________ Rivendell-dev mailing list [email protected]<mailto:[email protected]> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev _______________________________________________ Rivendell-dev mailing list [email protected]<mailto:[email protected]> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
