Hello Eric,
Monday, June 12, 2006, 11:21:24 PM, you wrote:
ES> I reproduced this pretty easily on a lab machine. I've filed:
ES> 6437568 ditto block repair is incorrectly propagated to root vdev
Good, thank you.
ES> To track this issue. Keep in mind that you do have a flakey
ES> controller/l
Hello Matthew,
Tuesday, June 13, 2006, 10:43:08 PM, you wrote:
MA> On Mon, Jun 12, 2006 at 12:58:17PM +0200, Robert Milkowski wrote:
>> I'm writing a script to do automatically snapshots and destroy old
>> one. I think it would be great to add to zfs destroy another option
>> so only snapsh
I believe ZFS is causing a panic whenever I attempt to mount an iso image (SXCR
build 39) that happens to reside on a ZFS file system. The problem is 100%
reproducible. I'm quite new to OpenSolaris, so I may be incorrect in saying
it's ZFS' fault. Also, let me know if you need any additional
Hello zfs-discuss,
NFS server on snv_39/SPARC, zfs filesystems exported.
Solaris 10 x64 clients (zfs-s10-0315), filesystems mounted from nfs
server using NFSv3 over TCP.
What I see from NFS clients is that mkdir operations to ZFS filesystems
could take even 20s! while to UFS exported fi
Sorry for resurrecting this interesting discussion so late: I'm skinning
backwards through the forum.
One comment about segregating database logs is that people who take their data
seriously often want a 'belt plus suspenders' approach to recovery.
Conventional RAID, even supplemented with ZF
On Tue, Jun 13, 2006 at 01:43:08PM -0700, Matthew Ahrens wrote:
> On Mon, Jun 12, 2006 at 12:58:17PM +0200, Robert Milkowski wrote:
> > I'm writing a script to do automatically snapshots and destroy old
> > one. I think it would be great to add to zfs destroy another option
> > so only snapsh
On Mon, Jun 12, 2006 at 12:58:17PM +0200, Robert Milkowski wrote:
> I'm writing a script to do automatically snapshots and destroy old
> one. I think it would be great to add to zfs destroy another option
> so only snapshots can be destroyed. Something like:
>
> zfs destroy -s SNAPSHOT
Noel Dellofano schrieb:
Out of curiosity, is this panic reproducible?
Hmm, not directly. The panic happened during a long running I/O stress test
in the middle of the night. The tests had already run for ~6 hours at that time.
> A bug should be filed on
this for more investigation. Feel fre
Out of curiosity, is this panic reproducible? A bug should be filed on
this for more investigation. Feel free to open one or I'll open it if
you forward me info on where the crash dump is and information on the
I/O stress test you were running.
thanks,
Noel :-)
***
