[zfs-discuss] Limiting the power of zfs destroy

2007-10-23 Thread Scott Laird
I'm writing a couple scripts to automate backups and snapshots, and I'm finding myself cringing every time I call 'zfs destroy' to get rid of a snapshot, because a small typo could take out the original filesystem instead of a snapshot. Would it be possible to add a flag (maybe -t type) to zfs

Re: [zfs-discuss] Limiting the power of zfs destroy

2007-10-23 Thread A Darren Dunham
On Tue, Oct 23, 2007 at 09:55:58AM -0700, Scott Laird wrote: I'm writing a couple scripts to automate backups and snapshots, and I'm finding myself cringing every time I call 'zfs destroy' to get rid of a snapshot, because a small typo could take out the original filesystem instead of a

Re: [zfs-discuss] Limiting the power of zfs destroy

2007-10-23 Thread Mark J Musante
On Tue, 23 Oct 2007, A Darren Dunham wrote: On Tue, Oct 23, 2007 at 09:55:58AM -0700, Scott Laird wrote: I'm writing a couple scripts to automate backups and snapshots, and I'm finding myself cringing every time I call 'zfs destroy' to get rid of a snapshot, because a small typo could take

Re: [zfs-discuss] Sequential vs Random I/O on array controller for ZFS usage

2007-10-23 Thread Roch Bourbonnais
Le 21 oct. 07 à 02:40, Vincent Fox a écrit : We had a Sun Engineer on-site recently who said this: We should set our array controllers to sequential I/O *even* if we are doing random I/O if we are using ZFS. This is because the Arc cache is already grouping requests up sequentially so