Re: selectively disabling atime updates?

2012-06-01 Thread Ignatios Souvatzis
On Thu, May 31, 2012 at 08:37:06AM -0700, Paul Goyette wrote: On Thu, 31 May 2012, Matthias Kretschmer wrote: On Thu, May 31, 2012 at 04:42:27PM +0200, Edgar Fuß wrote: How about using fss for it instead. 1. fss is still marked experimental. oh, I have overlooked that. 2. does fss work

Re: selectively disabling atime updates?

2012-06-01 Thread David Holland
On Thu, May 31, 2012 at 04:56:26PM +0200, Matthias Kretschmer wrote: How about using fss for it instead. 1. fss is still marked experimental. oh, I have overlooked that. I'm not sure that should stop you though. Or the marking should be removed. People use it, it seems to work, it's been

Re: selectively disabling atime updates?

2012-06-01 Thread Edgar Fuß
How about using fss for it instead. Well, the point is not that I primarily don't want the atimes to reflect the backup access. I primarily want to save the time spent on the update. A find is aproximately twice as fast with noatime.

Re: selectively disabling atime updates?

2012-06-01 Thread Paul Goyette
On Fri, 1 Jun 2012, Ignatios Souvatzis wrote: How about using fss for it instead. 1. fss is still marked experimental. oh, I have overlooked that. 2. does fss work with WAPL at all? I don't know that. It seems to work for me! All my FS are WAPBL-enabled, and I always use backup -X for

Re: Rump FS throughput

2012-06-01 Thread Thomas Klausner
On Thu, May 31, 2012 at 01:45:53PM -0400, Matthew Mondor wrote: Although it's useful to mount random media more safely than it would be using kernel-space, I noticed that using 64KB reads, the kernel cd9660 will gladly read ~20MB/s from a DVD, but that rump_cd9660 using 64KB reads is limited