Thanks for the reminder on atime. I promise to read the manuals closer in
the future!
Hans J. Albertsson
From my Nexus 5
Den 14 maj 2015 22:39 skrev David Brodbeck bro...@uw.edu:
Yeah, sorry, I admin a lot of Linux servers so I'm used to thinking of it
generically as 'noatime'. :)
On Thu,
Yeah, sorry, I admin a lot of Linux servers so I'm used to thinking of it
generically as 'noatime'. :)
On Thu, May 14, 2015 at 4:02 AM, James Carlson carls...@workingcode.com
wrote:
On 05/14/15 05:15, Hans J. Albertsson wrote:
noatime, isn't that a UFS specific mount option??
There's a ZFS
noatime, isn't that a UFS specific mount option??
Can this be done in mount_nfs??
On 2015-05-13 21:36, David Brodbeck wrote:
On Wed, May 13, 2015 at 4:33 AM, Udo Grabowski (IMK) udo.grabow...@kit.edu
wrote:
On 13/05/2015 09:20, Hans J. Albertsson wrote:
This is what it looks like on the
On 05/14/15 05:15, Hans J. Albertsson wrote:
noatime, isn't that a UFS specific mount option??
There's a ZFS equivalent:
% man zfs | grep atime
atime=on | off
atimeproperty
pool/home/bob atime on default
Can this be done in
On 05/13/15 03:20, Hans J. Albertsson wrote:
Tank/cifs@transfer_prep - 8.24M - -
- -
Tank/cifs@transfer1 - 966K - -
- -
I'd like to see what data is to blame for the 966K reported for
transfer1 as
On 13/05/2015 09:20, Hans J. Albertsson wrote:
This is what it looks like on the FreeNAS box
NAME AVAIL USED USEDSNAP USEDDS
USEDREFRESERV USEDCHILD
Tank/cifs8.93T 1.45T 9.18M
1.45T 0 0
Tank/cifs@transfer_prep
I'm trying (their patience...) already
On 2015-05-13 13:30, James Carlson wrote:
This might help:
http://www.freenas.org/support/
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
On Wed, May 13, 2015 at 4:33 AM, Udo Grabowski (IMK) udo.grabow...@kit.edu
wrote:
On 13/05/2015 09:20, Hans J. Albertsson wrote:
This is what it looks like on the FreeNAS box
NAME AVAIL USED USEDSNAP USEDDS
USEDREFRESERV USEDCHILD
Tank/cifs
This is what it looks like on the FreeNAS box
NAME AVAIL USED USEDSNAP USEDDS
USEDREFRESERV USEDCHILD
Tank/cifs8.93T 1.45T 9.18M
1.45T 0 0
Tank/cifs@transfer_prep - 8.24M - -
On 05/12/15 11:34, Chris Gerhard wrote:
On 12/05/2015 14:23, Hans J. Albertsson wrote:
I mean, I know about snapdir=visible and all that, but I want to look
at what data has been written to a dataset after the snapshot.
What I REALLY want to achieve is to see who is writing what to my
I mean, I know about snapdir=visible and all that, but I want to look at
what data has been written to a dataset after the snapshot.
What I REALLY want to achieve is to see who is writing what to my
dataset when it really shouldn't be written to!
On 05/12/15 09:23, Hans J. Albertsson wrote:
I mean, I know about snapdir=visible and all that, but I want to look at
what data has been written to a dataset after the snapshot.
The copy-on-write is done on a block basis, not a file basis. Blocks of
data don't point back to the files in which
On 12/05/2015 14:23, Hans J. Albertsson wrote:
I mean, I know about snapdir=visible and all that, but I want to look
at what data has been written to a dataset after the snapshot.
What I REALLY want to achieve is to see who is writing what to my
dataset when it really shouldn't be written to!
13 matches
Mail list logo
