Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 4
    If you are really sure what you state in your third paragraph is correct, that would be a bug with the BSD ZFS implementation. ZFS pool read only import was designed to be truly read-only, i.e. it never tries to write or fix any data or metadata, including the pool history. See arc.stillopensolaris.org/txt/PSARC_2010_306.txt Commented Jul 19, 2016 at 23:59
  • 1
    @jlliagre I'm quite sure, but it might have been in the context of some other ZFS implementation. I don't really see why they would differ in such a fundamental aspect, though; I believe all open-source ZFS implementations share a significant amount of code that traces its lineage back to Sun. I just might set up some kind of testing environment for this and poke at it with a stick then see what happens, but it will be some time before I can devote the time to actually do that. Commented Jul 20, 2016 at 7:45
  • 1
    The fact that I apparently have "import" to simple read a file in ZFS is what troubles me. I have a ZFS drive I am trying to access files from while the system it was originally in is unavailable. When that system is available again, I want to put the drive back in it and resume as if nothing had happened. But in the mean time I do need to access some of the files on the drive. Hopefully your answer provides the information I need for this particular use case. Commented May 6, 2023 at 19:48