> Your experience is exactly why I suggested ZFS start doing some "right > sizing" if you will. Chop off a bit from the end of any disk so that > we're guaranteed to be able to replace drives from different > manufacturers. The excuse being "no reason to, Sun drives are always > of identical size". If your drives did indeed come from Sun, their > response is clearly not true. Regardless, I guess I still think it > should be done. Figure out what the greatest variation we've seen from > drives that are supposedly of the exact same size, and chop it off the > end of every disk. I'm betting it's no more than 1GB, and probably > less than that. When we're talking about a 2TB drive, I'm willing to > give up a gig to be guaranteed I won't have any issues when it comes > time to swap it out.
My disks are sun branded intel disks. Same model number. The first replacement disk had a newer firmware, so we jumped to conclusion that was the cause of the problem, and caused oracle plenty of trouble in locating an older firmware drive in some warehouse somewhere. But the second replacement disk is truly identical to the original. Same firmware and everything. Only the serial number is different. Still the same problem behavior. I have reason to believe that both the drive, and the OS are correct. I have suspicion that the HBA simply handled the creation of this volume somehow differently than how it handled the original. Don't know the answer for sure yet. Either way, yes, I would love zpool to automatically waste a little space at the end of the drive, to avoid this sort of situation, whether it's caused by drive manufacturers, or HBA, or any other factor. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
