Hi there,
I might be missing something but I have not yet figured out how to use glabel(8) on a gjournal(8)'d UFS file system, since both seem to be fighting against each other for possession of the last sector of the disk slice or partition.
In fact, this post is raised after I made what appears to be a booboo x(
I had a perfectly working journaled filesystem (say, da0s1a.journal). Being one of several removable storage, I wanted to give it a comprehensive label for easyness's sake.
Well that was a mistake.
Not knowing whether I should be using either the GEOM provider (da0s1a.journal) or the underlying consumer (da0s1a), I went for the "physical" storage, and ran the following command on the unmounted da0s1a:
This worked perfectly fine, and "glabel status" showed in my newly labeled file system. So far, so good !
But gjournal(8) stopped recognizing da0s1a as a journalized file system, and the device /dev/da0s1a.journal simply no longer exists, no matter what I do: unloading/reloading gjournal, detaching/reattaching my removable media.
Therefore my two questions:
Thank you.
Cheers
Franck
I might be missing something but I have not yet figured out how to use glabel(8) on a gjournal(8)'d UFS file system, since both seem to be fighting against each other for possession of the last sector of the disk slice or partition.
In fact, this post is raised after I made what appears to be a booboo x(
I had a perfectly working journaled filesystem (say, da0s1a.journal). Being one of several removable storage, I wanted to give it a comprehensive label for easyness's sake.
Well that was a mistake.
Not knowing whether I should be using either the GEOM provider (da0s1a.journal) or the underlying consumer (da0s1a), I went for the "physical" storage, and ran the following command on the unmounted da0s1a:
# glabel label -v mylabel /dev/da0s1a
This worked perfectly fine, and "glabel status" showed in my newly labeled file system. So far, so good !
But gjournal(8) stopped recognizing da0s1a as a journalized file system, and the device /dev/da0s1a.journal simply no longer exists, no matter what I do: unloading/reloading gjournal, detaching/reattaching my removable media.
Therefore my two questions:
- (general) How does one go about labeling a g-journaled UFS file system ?
- (specific) In my actual situation, as described above, what are my options ? Should I revert to using soft-updates on da0s1, and forget about the journal, or is there a way to get the journal back together (initially set-up on the same slice as the data).
Thank you.
Cheers
Franck