e (eg. turn
on compression). However, we're aware that preserving the settings
would be really useful too, and we'll be working on that for a future
release.
Franz Haberhauer wrote:
Where are properties of a ZFS filesystem stored (e.g. non-default
mountpoints, quota, r
e
defaults somewhere
as they are done or save the output of a "zfs get" along with backups.
- Franz
Franz Haberhauer wrote:
Where are properties of a ZFS filesystem stored (e.g. non-default
mountpoints, quota, reservation, compression, exported shares etc.)?
Do backup/restore mecha
mewhere
as they are done or save the output of a "zfs get" along with backups.
- Franz
Franz Haberhauer wrote:
Where are properties of a ZFS filesystem stored (e.g. non-default
mountpoints, quota, reservation, compression, exported shares etc.)?
Do backup/restore mechanisms (zfs sen
Where are properties of a ZFS filesystem stored (e.g. non-default
mountpoints, quota, reservation,
compression, exported shares etc.)?
Do backup/restore mechanisms (zfs send/receive, Networker/NetBackup/TSM,
*tar etc.)
handle (save/restore) them automagically or are there additional
procedures
Nicolas Williams wrote:
On Sat, May 13, 2006 at 08:23:55AM +0200, Franz Haberhauer wrote:
Given that ISV apps can be only changed by the ISV who may or may not be
willing to
use such a new interface, having a "no cache" property for the file - or
given that filesystems
are now re
The problem I see with "sequential access jump all over the place" is
that this increases the utilization of the disks -
over the years disks have become even faster for sequential access,
whereas random access (as they have
to move the actuator) has not improved at the same pace - this is what
Given that ISV apps can be only changed by the ISV who may or may not be
willing to
use such a new interface, having a "no cache" property for the file - or
given that filesystems
are now really cheap with ZFS - for the filesystem would be important
as well,
like the forcedirectio mount option
>'ZFS optimizes random writes versus potential sequential reads.'
This remark focused on the allocation policy during writes,
not the readahead that occurs during reads.
Data that are rewritten randomly but in place in a sequential,
contiguos file (like a preallocated UFS file) are not optimi
Gregory Shaw wrote On 05/11/06 21:15,:
Regarding directio and quickio, is there a way with ZFS to skip the
system buffer cache? I've seen big benefits for using directio when
the data files have been segregated from the log files.
Having the system compete with the DB for read-ahead results
Roch Bourbonnais - Performance Engineering wrote On 05/12/06 09:30,:
Tao Chen writes:
> On 5/11/06, Peter Rival <[EMAIL PROTECTED]> wrote:
> > Richard Elling wrote:
> > > Oracle will zero-fill the tablespace with 128kByte iops -- it is not
> > > sparse. I've got a scar. Has this changed i
10 matches
Mail list logo
