First, this is under FreeBSD, but it isn''t specific to that OS, and it involves some technical details beyond normal use, so I''m trying my luck here. I have a pool (around version 14) with a corrupted log device that''s irrecoverable. I found a tool called logfix, but I don''t have the GUID of the log device stored anywhere, so it won''t work. My idea was to replace it with a dummy log device. I can easily create a new one, and I don''t think it''s actually tied to the pool. The way that seems to be implemented is vdevs store a checksum for the pool that includes the log device''s GUID (and possibly other things). If I make a new log device, would recalculating a pool checksum and replacing it on the devices at least get my pool to mount so I can recover the data? -- This message posted from opensolaris.org
----- Original Message -----> First, this is under FreeBSD, but it isn''t specific to that OS, and it > involves some technical details beyond normal use, so I''m trying my > luck here. > > I have a pool (around version 14) with a corrupted log device that''s > irrecoverable. I found a tool called logfix, but I don''t have the GUID > of the log device stored anywhere, so it won''t work.Last I checked, you lose the pool if you lose the slog on zpool versions < 19. I don''t think there is a trivial way around this. Vennlige hilsener / Best regards roy -- Roy Sigurd Karlsbakk (+47) 97542685 roy at karlsbakk.net http://blogg.karlsbakk.net/ -- I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et element?rt imperativ for alle pedagoger ? unng? eksessiv anvendelse av idiomer med fremmed opprinnelse. I de fleste tilfeller eksisterer adekvate og relevante synonymer p? norsk.
> From: zfs-discuss-bounces at opensolaris.org [mailto:zfs-discuss- > bounces at opensolaris.org] On Behalf Of Roy Sigurd Karlsbakk > > Last I checked, you lose the pool if you lose the slog on zpool > versions < 19. I don''t think there is a trivial way around this.You should plan for this to be true when you''re designing a system, because you can''t import the pool afterward etc... However ... The actual data on disk hasn''t disappeared. The only problem is the fact that you can''t import it. And the last ~30 sec of writes have actually been lost - not stored on disk anywhere. So, there *might* be some technique, reliable or not, which is able to import everything up to 30sec ago, despite failed log device. I don''t know the answer. My first guess would be (a) make a "dd" copy of all the disks in the pool, just to ensure you won''t be accidentally corrupting something irreversibly worse than it is now. (b) Try attaching those disks to a more modern system (maybe openindiana, or b134 of opensolaris, or solaris 10u9) maybe the more modern system can import... Aside from that, I don''t know.
> > From: zfs-discuss-bounces at opensolaris.org > [mailto:zfs-discuss- > > bounces at opensolaris.org] On Behalf Of Roy Sigurd > Karlsbakk > > > > Last I checked, you lose the pool if you lose the > slog on zpool > > versions < 19. I don''t think there is a trivial way > around this. > > The actual data on disk > hasn''t disappeared. The only problem is the fact > that you can''t import it.That''s what''s so frustrating. -- This message posted from opensolaris.org
If your pool is on version > 19 then you should be able to import a pool with a missing log device by using the ''-m'' option to ''zpool import''. - George On Sat, Oct 23, 2010 at 10:03 PM, David Ehrmann <ehrmann at gmail.com> wrote:> > > From: zfs-discuss-bounces at opensolaris.org > > [mailto:zfs-discuss- > > > bounces at opensolaris.org] On Behalf Of Roy Sigurd > > Karlsbakk > > > > > > Last I checked, you lose the pool if you lose the > > slog on zpool > > > versions < 19. I don''t think there is a trivial way > > around this. > > > > The actual data on disk > > hasn''t disappeared. The only problem is the fact > > that you can''t import it. > > That''s what''s so frustrating. > -- > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20101023/8f0eeb0e/attachment.html>
he''s using fbsd, so his pool is on v11 or something ----- Original Message ----- If your pool is on version > 19 then you should be able to import a pool with a missing log device by using the ''-m'' option to ''zpool import''. - George On Sat, Oct 23, 2010 at 10:03 PM, David Ehrmann < ehrmann at gmail.com > wrote:> > From: zfs-discuss-bounces at opensolaris.org > [mailto: zfs-discuss- > > bounces at opensolaris.org ] On Behalf Of Roy Sigurd > Karlsbakk > > > > Last I checked, you lose the pool if you lose the > slog on zpool > > versions < 19. I don''t think there is a trivial way > around this. > > The actual data on disk > hasn''t disappeared. The only problem is the fact > that you can''t import it.That''s what''s so frustrating. -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss at opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss _______________________________________________ zfs-discuss mailing list zfs-discuss at opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss -- Vennlige hilsener / Best regards roy -- Roy Sigurd Karlsbakk (+47) 97542685 roy at karlsbakk.net http://blogg.karlsbakk.net/ -- I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et element?rt imperativ for alle pedagoger ? unng? eksessiv anvendelse av idiomer med fremmed opprinnelse. I de fleste tilfeller eksisterer adekvate og relevante synonymer p? norsk. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20101024/59edc4fa/attachment.html>
How does ZFS detect that there''s a log device attached to a pool? I couldn''t actually find the GUID of the log device anywhere on the other devices in the pool. -- This message posted from opensolaris.org
On Sun, Oct 24, 2010 at 6:51 AM, Roy Sigurd Karlsbakk <roy at karlsbakk.net> wrote:> he''s using fbsd, so his pool is on v11 or somethingFreeBSD before 7.3 is ZFSv6. FreeBSD 7.3, 8.0, and 8.1 are ZFSv14. FreeBSD 8-STABLE (which will become 8.2) is ZFSv15. FreeBSD 9-CURRENT (which will become 9.0) has experimental patches available for ZFSv28. -- Freddie Cash fjwcash at gmail.com
The guid is stored on the mirrored pair of the log and in the pool config. If you''re log device was not mirrored then you can only find it in the pool config. - George On Sun, Oct 24, 2010 at 9:34 AM, David Ehrmann <ehrmann at gmail.com> wrote:> How does ZFS detect that there''s a log device attached to a pool? I > couldn''t actually find the GUID of the log device anywhere on the other > devices in the pool. > -- > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20101024/397f6d3b/attachment.html>