On Thu, Oct 04, 2007 at 08:36:10AM -0600, eric kustarz wrote: > > Client A > > - import pool make couple-o-changes > > > > Client B > > - import pool -f (heh) > > > > Client A + B - With both mounting the same pool, touched a couple of > > files, and removed a couple of files from each client > > > > Client A + B - zpool export > > > > Client A - Attempted import and dropped the panic. > > > > ZFS is not a clustered file system. It cannot handle multiple > readers (or multiple writers). By importing the pool on multiple > machines, you have corrupted the pool.
Yes. > You purposely did that by adding the '-f' option to 'zpool import'. > Without the '-f' option ZFS would have told you that its already > imported on another machine (A). > > There is no bug here (besides admin error :) ). My reading is that the complaint is not about corrupting the pool. The complaint is that once a pool has become corrupted, it shouldn't cause a panic on import. It seems reasonable to detect this and fail the import instead. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. > _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
