Hi, Thanks for the response, Here is my problem. I have a zfs stream back up took on zfs version 15, currently i have upgraded my OS, so new zfs version is 22. Restore process went well from old stream backup to new zfs pool. but on reboot i got error unable to mount pool tank. So there is incompatibilities between zfs versions, especially send/receive. So looking for alternate backup solutions. Thanks kumar -- This message posted from opensolaris.org
Hi, Thanks for the response, Here is my problem. I have a zfs stream back up took on zfs version 15, currently i have upgraded my OS, so new zfs version is 22. Restore process went well from old stream backup to new zfs pool. but on reboot i got error unable to mount pool tank. So there is incompatibilities between zfs versions, especially send/receive. So looking for alternate backup solutions. Thanks kumar -- This message posted from opensolaris.org
Sorry, I did not hit this type of error...
AFAIK the pool writes during zfs receive are done by current code (i.e. ZFSv22
for you) based on data read from the backup stream. So unless there are
corruptions on the pool which happened to be at the same time as you did your
restore, this procedure should not have broken your pool. It was just a
(special) write by your OS version''s code, nearly same as any other.
Did you have any hardware problems at that time, like brown-outs, overheating,
occasional push of a reset button?
Maybe some experts here would be able to comment better or guide you through
troubleshooting and collecting data, if you post your OS version details, error
messages especially, etc.
For example, if for some reason your hostid changed (i.e. you used the safe mode
miniroot) and the pool tank was not exported afterwards, the error may be like
"Pool is busy or used by another system" with a solution as simple as
that you''d have to do a forced import ("zpool import -f
tank") - if it is indeed a local non-networked pool and no other machine
really uses it.
HTH,
//Jim
--
This message posted from opensolaris.org
> From: zfs-discuss-bounces at opensolaris.org [mailto:zfs-discuss- > bounces at opensolaris.org] On Behalf Of Naveen surisetty > > I have a zfs stream back up took on zfs version 15, currently i haveupgraded> my OS, so new zfs version is 22. Restore process went well from old stream > backup to new zfs pool. but on reboot i got error unable to mount pooltank. Let me make sure I get this straight ... You did "zfs send" on zpool version 15, save to a file. Then you upgraded system and have zpool version 22. You do "zfs receive" and there are no errors. Simply having successfully completed the "zfs receive" should guarantee it was successfully received. But since you''re having a problem, I suggest you "zpool export" and "zpool import" immediately after doing your zfs receive. If you''re able to do this, it guarantees the pool is in fact importable. Then if you reboot and encounter a problem, you know you''re running into something else that''s weird. Like perhaps unsupported or buggy hardware that does something bad to disk during the reboot process.
On May 10, 2011, at 11:21 PM, Naveen surisetty wrote:> Hi, > > Thanks for the response, Here is my problem. > > I have a zfs stream back up took on zfs version 15, currently i have upgraded my OS, so new zfs version is 22. Restore process went well from old stream backup to new zfs pool. but on reboot i got error unable to mount pool tank.There is no such thing as "mounting a pool" Can you post the exact error message? -- richard
> From: zfs-discuss-bounces at opensolaris.org [mailto:zfs-discuss- > bounces at opensolaris.org] On Behalf Of Naveen surisetty > > I have a zfs stream back up took on zfs version 15, currently i haveupgraded> my OS, so new zfs version is 22. Restore process went well from old stream > backup to new zfs pool. but on reboot i got error unable to mount pooltank.> > So there is incompatibilities between zfs versions, especiallysend/receive.> > So looking for alternate backup solutions.Sorry, not correct. As Richard said, please post the exact error message you are seeing, because what you said, the way you said it, doesn''t make sense. And since I just posted this a minute ago in a different thread, I''ll just quote myself again here: Years ago, there was a comment in the man page that said this: "The format of the stream is evolving. No backwards compatibility is guaranteed. You may not be able to receive your streams on future versions of ZFS." But in the last several years, backward/forward compatibility has always been preserved, so despite the warning, it was never a problem. In more recent versions, the man page says: "The format of the stream is committed. You will be able to receive your streams on future versions of ZFS."