I hate to bitch but bitch I must
af.gourmet at videotron.ca
Fri Oct 16 23:11:01 UTC 2009
Manolis Kiagias wrote:
> PJ wrote:
>> Why is it that the manual pages, as thorough as they may be, are very,
>> very confusing.
>> Perhaps I am being too wary, but I find that too many
>> instructions/examples are stumbling blocks to appreciation of the whole
>> for instance, let's look at the instructions for changing disk labels
>> with glabel or is it tunefs ?
>> man glabel(8):
>> for UFS the file system label is set with
>> what happened to glabel?
>> man tunefs(8)
>> The *tunefs* utility cannot be
>> run on an active file system. To change an active file system, it must
>> be downgraded to read-only or unmounted.
>> So, you have to run tunefs from an active file system to modify another
>> but from man tunefs:
>> This utility should work on active file systems.
>> What in hades does this mean--just above it says cannot be run on active
>> file systems. ???
>> To change the root file
>> system, the system must be rebooted after the file system is tuned.
>> You can tune a file system, but you cannot tune a fish.
>> How cute... And fish eat bugs.
>> Seriously, now to the manual:
>> To create a permanent label for a UFS2 file system without destroying
>> any data, issue the following command:
>> # tunefs -L /home/ /dev/da3
>> Oh? home is what? What does this have to do with the partitions?
>> Here's from man glabel(8):
>> The following example shows how to set up a label for disk ``da2'', cre-
>> ate a file system on it, and mount it:
>> glabel label -v usr /dev/da2
>> newfs /dev/label/usr
>> mount /dev/label/usr /usr
>> umount /usr
>> glabel stop usr
>> glabel unload
>> The next example shows how to set up a label for a UFS file system:
>> tunefs -L data /dev/da4s1a
>> mount /dev/ufs/data /mnt/data
>> Am I to understand that glabel is only for a new system? What's with the
>> newfs... I'm trying to set labels on an system that is already set up.
>> And, the glabel examle above is not for UFS file systems? Oh, that's for
>> So why are we even dealing with this glabel?
>> from manual:
>> # tunefs -L /home/ //dev/da3/
>> A label should now exist in /dev/ufs which may be added to /etc/fstab:
>> /dev/ufs/home /home ufs rw 2 2
>> Why? Is this necessary? and somewhere I saw "tunefs -L volume
>> /dev/da0s1a" or something like that. Does that mean that each partition
>> should be tunefsd? Maybe the guys who programmed this stuff understand;
>> I sure don't. I just want to be able to set the labels according to what
>> they say can be done... so shy not have a clear and concise explanation?
> Relax. You are having a bad day, and you are topping it by trying to
> perform some stuff while you are not in the right state of mind.
> If you do insist on continuing with this, do the following:
> Make a list of your partitions - I'll assume a device name of /dev/ad1
> for the disk. You should have:
> ad1s1a for root => Label this as rootfs
> ad1s1b for swap => Label this as swap
> ad1s1e for tmp => Label this as tmpfs
> ad1s1d for var => Label this as varfs
> ad1s1f for usr => Label this as usrfs
> If you are unsure of the device names, try ls /dev/ad* (or ls /dev/da*
> if you are using SCSI disks, which I think you are not)
> Now, reboot:
> shutdown -r now
> Press 4 and enter single user mode in the loader.
> In the single user mode prompt type:
> glabel label rootfs /dev/ad1s1a
> glabel label swap /dev/ad1s1b
> glabel label tmpfs /dev/ad1s1e
> glabel label varfs /dev/ad1s1d
> glabel label usrfs /dev/ad1s1f
> You should get no error messages from these.
> Type exit and continue to multiuser boot.
Ok, but that is exactly what I did. Exactly that and that is what is in
the manual. And I can read and I did check and recheck my input for
typos. But, I did get error messages!
# glabel label rootfs/dev/ad12s1a
glabel: Can't store metadata on /dev/ad12s1a: Operation not permitted
and the message was the same for all partitions!
So, you must wonder as I did why was I getting error messages. I looked
on the web and there was nothing directly related to the errors.So what
is going on?
Since the web gurus were saying that the error messages were not
important and to ignore them, I tried that and continued through with
the boot and changed the fstab entries and rebooted and the boot failed.
So I had to fix the fstab and fortunately I was able to boot ok...
Something is warped here... and I hope it isn't my little brain. :-(
> Change /etc/fstab:
> /dev/ad1s1a to /dev/label/rootfs
> /dev/ad1s1b to /dev/label/swap
> and so on.
> Reboot once again. Everything should work.
>> Do people who write this stuff ever read it? Tell me t
> Yes, we do. All the time actually.
>> hat its clear and
>> simple and to the point... so far, I have been running back and forth
>> between half a dozen web pages trying to understand what is going on...
>> and doing things through a dense fog does not produce creative
> You will have best results when trying with a clear mind.
> Also having a test system (or a VMware / Virtualbox machine) will help
> you learn and practice unknown procedures without the anxiety of
> breaking something on your production system.
Manolis, my state of mind is quite clear... and I'm coping with
everything quite allright... I'm not about to get mad at anyone or
but tell me, honestly, when you see the stuff I have described above?
Woldn't that confuse anyone in their right mind?
More information about the freebsd-questions