Timeline for Cannot mount btrfs subvolume
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 9, 2024 at 12:58 | vote | accept | Zak | ||
| May 17, 2023 at 9:55 | comment | added | Zak |
Thanks, @KamilMaciorowski. I read somewhere to prefer subvol over subvolid, but I can't find the source right now. I believe it had to do with snapshots, which are created and removed, or switched out when reverting to previous versions, in which case a different subvolid becomes associated with a given subvolume path. At least for testing, it can be pretty helpful, though.
|
|
| May 17, 2023 at 7:58 | history | edited | Zak | CC BY-SA 4.0 |
missing "the"
|
| May 14, 2023 at 5:47 | comment | added | Kamil Maciorowski |
I guess an alternative way is with subvolid=256 instead of subvol=…. The subvolume listing is not misleading in this matter. Especially in case of many, many nested subvolumes it will be way easier to use the ID of the subvolume you're after instead of building the path backwards node by node.
|
|
| May 14, 2023 at 5:43 | history | edited | Kamil Maciorowski | CC BY-SA 4.0 |
improved formatting, capitalization, style; removed credit
|
| May 14, 2023 at 0:45 | history | answered | Zak | CC BY-SA 4.0 |