Volume manager blows the hell up
Nice to have
Reason for Closing:
Reason for Blocked:
Support Suite Ticket:
Trying to create new pool on 10.5.0.125 (my usual root pw) - destroyed old pool and said to mark drives as destroyed. This worked. Dragged new drives into a RAIDZ2 + L2ARC and said to create volume tank.
Deal with there being dead symlinks to old pools for the NFSv4 stablerestart files. The root cause of the buggy behavior is that os.path.exists() returns False for dead symlinks; it follows the symlink. Because the programmer that wrote the code assumed that os.path.exists would return True if the symlink was there (regardless if it was valid or not) the code would try to create a symlink where one already existed and explode with a glorious traceback. Ticket: #6008