Re: [zfs-discuss] Another user looses his pool (10TB) in this case and 40 days work

Hello, I'm now thinking there is some _real_ bug in the way zfs handles files systems created with the pool itself (ie tank filesystem when zpool is tank, usually mounted as /tank) My own experiens shows that zfs is unable to send/receive recursively (snapshots, child fs) properly when the desti

Re: [zfs-discuss] zfs receive : is this expected ?

OK FORGET IT... I MUST BE VERY TIRED AND CONFUSED ;-( -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Re: [zfs-discuss] zfs receive : is this expected ?

I have additional problem, whicxh worries me. I tried different ways of sending/receiving my data pool. I took some snapshots, sent them, then destroyed them, using destroy -r. AFAIK this shoud not have affected the filesystem's _current_ state or am I mislead ? Now I succeeded to send a snapsho

Re: [zfs-discuss] zfs receive : is this expected ?

actually I succeded using : # zfs create ezdata/data # zfs send -RD d...@prededup | zfs recv -duF ezdata/data I still have to check the result, though -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org h

Re: [zfs-discuss] zfs receive : is this expected ?

Sorry if my question was confused. Yes I'm wondering about the catch22 resulting of the two errors : it means we are not able to send/receive a pool's root filesystem without using -F. The zpool list was just meant to say it was a whole pool... Bruno -- This message posted from opensolaris.org _

[zfs-discuss] zfs receive : is this expected ?

amber ~ # zpool list data NAME SIZE ALLOC FREECAP DEDUP HEALTH ALTROOT data 930G 295G 635G31% 1.00x ONLINE - amber ~ # zfs send -RD d...@prededup |zfs recv -d ezdata cannot receive new filesystem stream: destination 'ezdata' exists must specify -F to overwrite it amber ~

Re: [zfs-discuss] zfs send/receive : panic and reboot

you might imagine we get a lot of files uploaded named vmcore.1 You might also create a defect report at http://defect.opensolaris.org/bz/ Lori On 02/08/10 09:41, Bruno Damour wrote: I kept on trying to migrate my pool with children (see previous threads) and had the (bad) idea to try the

[zfs-discuss] zfs send/receive : panic and reboot

I kept on trying to migrate my pool with children (see previous threads) and had the (bad) idea to try the -d option on the receive part. The system reboots immediately. Here is the log in /var/adm/messages Feb 8 16:07:09 amber unix: [ID 836849 kern.notice] Feb 8 16:07:09 amber ^Mpanic[cpu1]/t

Re: [zfs-discuss] help with zfs send/receive

d tank/nas/vi...@base | zfs receive tank/test/Video This did what i neededi hope this helps On Sun, Feb 7, 2010 at 6:48 AM, Bruno Damour <mailto:br...@ruomad.net>> wrote: Hello, I'm trying to migrate my "data" pool to get dedup and compression. I tried

Re: [zfs-discuss] help with zfs send/receive

No success, I tried with -F thought I do not like these tricks, but now it complains about snapshost existing in destination. Destination did not exist before, so what ? -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discus

[zfs-discuss] help with zfs send/receive

Hello, I'm trying to migrate my "data" pool to get dedup and compression. I tried : # zfs send -RD d...@prededup |zfs receive ezdata/data it fails in the end with : cannot receive new filesystem stream: destination 'ezdata/data' exists must specify -F to overwrite it the ezdata pool has just been