In this last iteration, I switched to a completely different box with twice the resources. Somehow, from the symptoms, I don't think trying it on one of the 48 or 128GB servers at work is going to change the outcome. The hang happens too fast. it seems like something in the destroy is causing this system hang. ON this last iteration I also used a LIVE dvd of b130 on the 8gb system as another person in this thread who experienced the problem was able to use to get his pool back. AS far as hardware errors, since I used a completely different system for this last import nothing was the same except for disks, and even then I used only 1/2 the mirrored disks from the pool and tried import on each half. The reason I am only using half of the mirrored disks is so that if in my experimenting trying to get my data back I screw up the pool, I still have a copy of the pool to use for later tests.
Also, to any devs, there is a thread on here where a user is also experiencing the problem and he is offering up his server for remote access for a dev to check out the problem. after 4 days, I stopped the import as it was just sort of sitting there hung. Anyone know if I can import a pool without the log device? I'd like to try that next if there is some way to do that. -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
