Actions
Bug #6183
closed
VERIFY3(newds==os->os_dsl_dataset) failed@dmu_objset.c:579
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
zfs - Zettabyte File System
Start date:
2015-08-31
Due date:
% Done:
0%
Estimated time:
Difficulty:
Bite-size
Tags:
needs-triage
Gerrit CR:
Description
Very old dataset upgrade path, fails with:
VERIFY3 " "failed ("
"0xffffff824e87a100" " " "==" " " "0xffffff824e87b980" ")\n"@dmu_objset.c:579
Can be triggered with:
mkfile 256m filepool.bin
zpool create -o version=1 -O version=1 fp `pwd`/filepool.bin
zfs upgrade -V 2 fp
zfs upgrade -V 3 fp
zpool upgrade -V 9 fp
zfs upgrade -V 3 fp
zfs upgrade -V 4 fp
zpool upgrade -V 15 fp
zfs upgrade -V 4 fp
triggers on IllumOS, ZOL, FreeBSD and OS X.
Removing the VERIFY does technically stop it from causing a panic, and the
pool/dataset is upgraded, but, well, I don't know if there are side-effects
from doing that.
Updated by
Updated by Igor Kozhukhov almost 4 years ago
- Status changed from New to Closed
owner request to close it
Actions