From owner-freebsd-questions@FreeBSD.ORG Sat Oct 17 22:43:45 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 337D31065670 for ; Sat, 17 Oct 2009 22:43:45 +0000 (UTC) (envelope-from kraduk@googlemail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155]) by mx1.freebsd.org (Postfix) with ESMTP id 8ED368FC18 for ; Sat, 17 Oct 2009 22:43:44 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id 22so738292fge.13 for ; Sat, 17 Oct 2009 15:43:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=r2z9mmNEA5X2Y1ZCRLqF1Zf9nDbO4h2mt/eCLUDfdCY=; b=HBe0tWoX/7oXDM312LFNVoegUyeS4RLdXeiI8WTwCGHXEptoxUzvUzZCOPDuJPkon1 j/O8w+NTpOkUVw8Avco5c74JxOdtM6rdWjAXgZdUSt79eE/tzAyNMV8k/8Vk1Y2FpnV5 qcIauN506bdpCISPtnyfVymylVYSgf77n1Xnw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=w+PVAAAIZEXQG8AGPrKqBY1igniRMf5kLCrmltVzgPh4ELhIAfXKs5WTPOqyfwB/zb h7+slvzYruAug0o6EGR7FvR6dhi89FbXZaPOQMgU7ipRJlNmQQRoj1pqZDLGE7wApBq6 sOok33M7NYW65QFjCKc0dHkN8bj7n1foVSWGc= MIME-Version: 1.0 Received: by 10.239.181.163 with SMTP id m35mr276605hbg.175.1255819423416; Sat, 17 Oct 2009 15:43:43 -0700 (PDT) In-Reply-To: <4ADA32D2.2020802@videotron.ca> References: <4AD8EB8F.9010900@videotron.ca> <4AD8F651.1000001@otenet.gr> <4AD8FD82.8050306@videotron.ca> <4AD90066.60606@otenet.gr> <4ADA32D2.2020802@videotron.ca> Date: Sat, 17 Oct 2009 23:43:43 +0100 Message-ID: From: krad To: PJ Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Manolis Kiagias , "freebsd-questions@freebsd.org" Subject: Re: I hate to bitch but bitch I must X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Oct 2009 22:43:45 -0000 2009/10/17 PJ > Manolis Kiagias wrote: > > PJ wrote: > > > >> 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 > >> anything... > >> but tell me, honestly, when you see the stuff I have described above? > >> Woldn't that confuse anyone in their right mind? > >> > >> > >> > > > > I am sorry, but there is something here, either some mistake on your > > part or some other weird problem on your system I can not think of. > > > > I don't seem to remember glabel ever failing to store metadata, unless > > 1) The device is non-existing 2) The device is mounted. > > As a matter of fact, I did the glabel stuff on a machine a few hours > > ago. This was already fully installed, I rebooted single user and was > > done in less than 2 minutes. > > And yes, if you get a metadata error, it means nothing was done so you > > are *not* to go and change fstab! > > > > Could you please send us /etc/fstab and the results of ls /dev/ad* > > > Here are the outputs: > > fstab: > # Device Mountpoint FStype Options Dump Pass# > /dev/ad12s1b none swap sw 0 0 > /dev/ad12s1a / ufs rw 1 1 > /dev/ad12s1h /backups ufs rw 2 2 > /dev/ad12s1g /home ufs rw 2 2 > /dev/ad12s1d /tmp ufs rw 2 2 > /dev/ad12s1f /usr ufs rw 2 2 > /dev/ad12s1e /var ufs rw 2 2 > /dev/acd0 /cdrom cd9660 ro,noauto 0 0 > linproc /usr/compat/linux/proc linprocfs rw 0 0 > > df: > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/ad12s1a 2026030 319112 1544836 17% / > devfs 1 1 0 100% /dev > /dev/ad12s1h 50777034 4 46714868 0% /backups > /dev/ad12s1g 50777034 6276538 40438334 13% /home > /dev/ad12s1d 4058062 36 3733382 0% /tmp > /dev/ad12s1f 50777034 5729324 40985548 12% /usr > /dev/ad12s1e 2026030 176070 1687878 9% /var > linprocfs 4 4 0 100% /usr/compat/linux/proc > > # ls /dev/ad* > crw-r----- 1 root operator 0, 97 Oct 17 16:36 /dev/ad0 > crw-r----- 1 root operator 0, 103 Oct 17 16:36 /dev/ad0s1 > crw-r----- 1 root operator 0, 101 Oct 17 16:36 /dev/ad10 > crw-r----- 1 root operator 0, 106 Oct 17 16:36 /dev/ad10s1 > crw-r----- 1 root operator 0, 121 Oct 17 16:36 /dev/ad10s1a > crw-r----- 1 root operator 0, 122 Oct 17 16:36 /dev/ad10s1b > crw-r----- 1 root operator 0, 123 Oct 17 16:36 /dev/ad10s1c > crw-r----- 1 root operator 0, 124 Oct 17 16:36 /dev/ad10s1d > crw-r----- 1 root operator 0, 125 Oct 17 16:36 /dev/ad10s1e > crw-r----- 1 root operator 0, 126 Oct 17 16:36 /dev/ad10s1f > crw-r----- 1 root operator 0, 127 Oct 17 16:36 /dev/ad10s1g > crw-r----- 1 root operator 0, 102 Oct 17 16:36 /dev/ad12 > crw-r----- 1 root operator 0, 107 Oct 17 16:36 /dev/ad12s1 > crw-r----- 1 root operator 0, 128 Oct 17 16:36 /dev/ad12s1a > crw-r----- 1 root operator 0, 129 Oct 17 16:36 /dev/ad12s1b > crw-r----- 1 root operator 0, 130 Oct 17 16:36 /dev/ad12s1c > crw-r----- 1 root operator 0, 131 Oct 17 16:36 /dev/ad12s1d > crw-r----- 1 root operator 0, 132 Oct 17 16:36 /dev/ad12s1e > crw-r----- 1 root operator 0, 133 Oct 17 16:36 /dev/ad12s1f > crw-r----- 1 root operator 0, 134 Oct 17 16:36 /dev/ad12s1g > crw-r----- 1 root operator 0, 135 Oct 17 16:36 /dev/ad12s1h > crw-r----- 1 root operator 0, 99 Oct 17 16:36 /dev/ad4 > crw-r----- 1 root operator 0, 104 Oct 17 16:36 /dev/ad4s1 > crw-r----- 1 root operator 0, 108 Oct 17 16:36 /dev/ad4s1a > crw-r----- 1 root operator 0, 109 Oct 17 16:36 /dev/ad4s1b > crw-r----- 1 root operator 0, 110 Oct 17 16:36 /dev/ad4s1c > crw-r----- 1 root operator 0, 111 Oct 17 16:36 /dev/ad4s1d > crw-r----- 1 root operator 0, 112 Oct 17 16:36 /dev/ad4s1e > crw-r----- 1 root operator 0, 113 Oct 17 16:36 /dev/ad4s1f > crw-r----- 1 root operator 0, 114 Oct 17 16:36 /dev/ad4s1g > crw-r----- 1 root operator 0, 100 Oct 17 16:36 /dev/ad6 > crw-r----- 1 root operator 0, 105 Oct 17 16:36 /dev/ad6s1 > crw-r----- 1 root operator 0, 115 Oct 17 16:36 /dev/ad6s1a > crw-r----- 1 root operator 0, 116 Oct 17 16:36 /dev/ad6s1b > crw-r----- 1 root operator 0, 117 Oct 17 16:36 /dev/ad6s1c > crw-r----- 1 root operator 0, 118 Oct 17 16:36 /dev/ad6s1d > crw-r----- 1 root operator 0, 119 Oct 17 16:36 /dev/ad6s1e > crw-r----- 1 root operator 0, 120 Oct 17 16:36 /dev/ad6s1f > > Sorry, but I don't see what this is going to tell you... ad0 is XP; ad10 > is minimal FreeBSD 7.2; ad12 is 7.2 on 500gb; ad4 is 7.2 on 80gb; and > ad6 is messed up FBSD I'm cheking & setting up with clone of ad12 > (dump/restore) > Now I will try the glabel again... > # shutdown now > # glabel label rootfs /dev/ad12s1a > glabel: Can't store metadata on /dev/ad0s1a > > manual: "it is assumed that a single ATA disk is used, which is > currently recognized by the system as ad0. It is also assumed that the > standard FreeBSD partition scheme is used, with /, /var, /usr and /tmp > file systems, as well as a swap partition." > > Now, does that mean that glabel does not work if there are several disks > on the system... it certainly does not say so nor does it adv ertise > that this would not work if there are several ATA disks present.. > Previously I had also tried a reboot press 4 with exactly the same > results.... > > So, what am I doing wrong... or where is the system screwed up... from > my point of view, everything seems to work ok including Firefox, > flashplugin, Openoffice, gimp, netbeans, etc. etc. etc. even conky... :-) > > Perhaps this is just a frustrating mental exercise as the system works > without glabeling partitions... it just would save some work if it could > be implemented... then, if I were to look at it as a businessman... why > am I wasting so much time, energy and mental suffering when just > changing a few files will do the same thing and take less effort... > ohhhhh! what price intellectual curiosity..... ;-) > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" > come on its not hard !!! USE TUNEFS im pure zfs but with a little zvol trickery $ zfs create -V 10m test cannot open 'test': no such pool (root@carrera)-(23:39:18)-(~) 1 $ zfs create -V 10m system/test (root@carrera)-(23:39:26)-(~) 0 $ newfs /dev/zvol/system/test /dev/zvol/system/test: 10.0MB (20480 sectors) block size 16384, fragment size 2048 using 4 cylinder groups of 2.52MB, 161 blks, 384 inodes. super-block backups (for fsck -b #) at: 160, 5312, 10464, 15616 (root@carrera)-(23:39:44)-(~) 0 $ glabel status Name Status Components gptid/6d1d4467-7476-11de-a02b-001e8ca9b6e7 N/A ad5p1 gptid/55345c70-426b-11de-935d-001e8ca9b6e7 N/A ad7p1 ufsid/4a0f39b2979e06b6 N/A ad7 ufsid/4ada47b0b2c40249 N/A zvol/system/test (root@carrera)-(23:39:51)-(~) 0 $ tunefs -L test zvol/system/test (root@carrera)-(23:40:09)-(~) 0 $ glabel status Name Status Components gptid/6d1d4467-7476-11de-a02b-001e8ca9b6e7 N/A ad5p1 gptid/55345c70-426b-11de-935d-001e8ca9b6e7 N/A ad7p1 ufsid/4a0f39b2979e06b6 N/A ad7 ufsid/4ada47b0b2c40249 N/A zvol/system/test ufs/test N/A zvol/system/test (root@carrera)-(23:40:10)-(~) 0 $ mount /dev/ufs/test /mnt (root@carrera)-(23:40:24)-(~) 0 $ df | grep test /dev/ufs/test 19292 8 17744 0% /mnt or $ newfs -L test2 /dev/zvol/system/test /dev/zvol/system/test: 10.0MB (20480 sectors) block size 16384, fragment size 2048 using 4 cylinder groups of 2.52MB, 161 blks, 384 inodes. super-block backups (for fsck -b #) at: 160, 5312, 10464, 15616 (root@carrera)-(23:43:02)-(~) 0 $ glabel status Name Status Components gptid/6d1d4467-7476-11de-a02b-001e8ca9b6e7 N/A ad5p1 gptid/55345c70-426b-11de-935d-001e8ca9b6e7 N/A ad7p1 ufsid/4a0f39b2979e06b6 N/A ad7 ufsid/4ada48764edb7e70 N/A zvol/system/test ufs/test2 N/A zvol/system/test if you cant master glabel you should really et another job