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*
-
4If 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.txtjlliagre– jlliagre2016-07-19 23:59:03 +00:00Commented 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.user– user2016-07-20 07:45:53 +00:00Commented Jul 20, 2016 at 7:45
-
1The 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.Michael– Michael2023-05-06 19:48:58 +00:00Commented May 6, 2023 at 19:48
Add a comment
|
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. shell-script), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you