Re: glabel+gmirror (8.0-RC1 problem)
On Mon, Oct 05, 2009 at 07:33:40PM +0200, Oliver Lehmann wrote: gjorunal is also affected. I tried to use one partition of my gmirror disk as journal device for my 3ware raid-5 device which works until I reboot - the journal is then gone as well. Is this patch likly to fix this as well? Will it be included in a future RC? Until now I've stayed away using glabel+gmirror but I didn't knew that gjournal is affected as well so I'm now left with warning that the journal provider is gone wile booting - and more tragically I'm left without journaling at all (which hurts on a 2.7TB partition when the system was not cleanly shut down) I just committed the patch. Yes, it should fix gjournal case as well. I want to merge it before 8.0-RELEASE. -- Pawel Jakub Dawidek http://www.wheel.pl p...@freebsd.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! pgpD9y01pT9QM.pgp Description: PGP signature
Re: glabel+gmirror (8.0-RC1 problem)
Pawel Jakub Dawidek wrote: On Mon, Sep 28, 2009 at 08:37:56PM +0200, Oliver Lehmann wrote: Hi Pawel, Pawel Jakub Dawidek wrote: Does anything change between you upgrade from BETA3 and RC1? For example gmirror was compiled into the kernel before and now is loaded as module or something similar? Nope, it was a clean BETA3 installation with the default GENERIC kernel which has afaik geom_label in kernel, but not geom_mirror (nevertheless I loaded geom_label.ko at boottime as well as geom_mirror) The same with RC1 - clean and fresh installation with the default GENERIC kernel and geom_label in kernel (default), but still loaded as module at boottime as well as geom_mirror. Could you test this patch: http://people.freebsd.org/~pjd/patches/improved_taste.patch This makes gmirror+glabel work again on RC1 Thanks for confirmation. gjorunal is also affected. I tried to use one partition of my gmirror disk as journal device for my 3ware raid-5 device which works until I reboot - the journal is then gone as well. Is this patch likly to fix this as well? Will it be included in a future RC? Until now I've stayed away using glabel+gmirror but I didn't knew that gjournal is affected as well so I'm now left with warning that the journal provider is gone wile booting - and more tragically I'm left without journaling at all (which hurts on a 2.7TB partition when the system was not cleanly shut down) -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: glabel+gmirror (8.0-RC1 problem)
Oliver Lehmann lehm...@ans-netz.de writes: I noticed that even when I boot in multiuser, change fstab, then return into single user mode and remount / read-only, the label cannot be set. I need to boot directly into single user mode. Looks like writing the label is denied when the partition was once mounted rw before - even if it is actually mounted ro. IIRC, the underlying GEOM is promoted from ro to rw when you mount the file system, but it is never demoted back to ro. I don't know if that's fixable. DES -- Dag-Erling Smørgrav - d...@des.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: glabel+gmirror (8.0-RC1 problem)
On Sun, Sep 27, 2009 at 10:37:25PM +0200, Oliver Lehmann wrote: Hi, that gmirror together with glabel cannot be used looks like a problem introduced with 8.0-RC1 to me. [...] Does anything change between you upgrade from BETA3 and RC1? For example gmirror was compiled into the kernel before and now is loaded as module or something similar? Could you test this patch: http://people.freebsd.org/~pjd/patches/improved_taste.patch -- Pawel Jakub Dawidek http://www.wheel.pl p...@freebsd.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! pgpSxWihIdQz0.pgp Description: PGP signature
Re: glabel+gmirror (8.0-RC1 problem)
Pawel Jakub Dawidek p...@freebsd.org writes: Oliver Lehmann lehm...@ans-netz.de writes: that gmirror together with glabel cannot be used looks like a problem introduced with 8.0-RC1 to me. Does anything change between you upgrade from BETA3 and RC1? For example gmirror was compiled into the kernel before and now is loaded as module or something similar? Looks like the same issue I mentioned to you (pjd) last night. In my case, it was an upgrade from a week-old head to last night's head, and the only change was that the new kernel had NFS compiled in. Both the old and the new kernel loaded geom_label and geom_mirror as modules. Could you test this patch: http://people.freebsd.org/~pjd/patches/improved_taste.patch Works for me. DES -- Dag-Erling Smørgrav - d...@des.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: glabel+gmirror (8.0-RC1 problem)
Hi Pawel, Pawel Jakub Dawidek wrote: Does anything change between you upgrade from BETA3 and RC1? For example gmirror was compiled into the kernel before and now is loaded as module or something similar? Nope, it was a clean BETA3 installation with the default GENERIC kernel which has afaik geom_label in kernel, but not geom_mirror (nevertheless I loaded geom_label.ko at boottime as well as geom_mirror) The same with RC1 - clean and fresh installation with the default GENERIC kernel and geom_label in kernel (default), but still loaded as module at boottime as well as geom_mirror. Could you test this patch: http://people.freebsd.org/~pjd/patches/improved_taste.patch This makes gmirror+glabel work again on RC1 One thing which I noticed. I labeled in single user mode, my root partition with tunefs - as well as all my other partitions. After this was done, I remounted my root partition (mount -rw /) and changed my fstab to use the new geom labels instead. But somehow this killed the new root-label of my mirror/gm0s1a partition. After I rebooted, the label was gone and I had to manually specify the root partition ufs:mirror/gm0s1a to mount. All the labels of my other mirrored partitions where there (usr, tmp, var). I then rebooted once more into single user mode (specified once more the root partition manually) and did a tunefs -L once more. Then I rebooted directly and the label is now there. Is it possible that mount -rw / (which remounts /dev/mirror/gm0s1a) could have been killed the freshly given label? -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: glabel+gmirror (8.0-RC1 problem)
On Mon, Sep 28, 2009 at 08:37:56PM +0200, Oliver Lehmann wrote: Hi Pawel, Pawel Jakub Dawidek wrote: Does anything change between you upgrade from BETA3 and RC1? For example gmirror was compiled into the kernel before and now is loaded as module or something similar? Nope, it was a clean BETA3 installation with the default GENERIC kernel which has afaik geom_label in kernel, but not geom_mirror (nevertheless I loaded geom_label.ko at boottime as well as geom_mirror) The same with RC1 - clean and fresh installation with the default GENERIC kernel and geom_label in kernel (default), but still loaded as module at boottime as well as geom_mirror. Could you test this patch: http://people.freebsd.org/~pjd/patches/improved_taste.patch This makes gmirror+glabel work again on RC1 Thanks for confirmation. One thing which I noticed. I labeled in single user mode, my root partition with tunefs - as well as all my other partitions. After this was done, I remounted my root partition (mount -rw /) and changed my fstab to use the new geom labels instead. But somehow this killed the new root-label of my mirror/gm0s1a partition. After I rebooted, the label was gone and I had to manually specify the root partition ufs:mirror/gm0s1a to mount. All the labels of my other mirrored partitions where there (usr, tmp, var). I then rebooted once more into single user mode (specified once more the root partition manually) and did a tunefs -L once more. Then I rebooted directly and the label is now there. Is it possible that mount -rw / (which remounts /dev/mirror/gm0s1a) could have been killed the freshly given label? Yes. tunefs(8) updates only on-disk super-block, but the kernel holds super-block that was read before. Now when you do 'mount -rw /' the in-kernel super-block is stored to the disk, and there is nothing about your label in there, so it gets overwritten. -- Pawel Jakub Dawidek http://www.wheel.pl p...@freebsd.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! pgpxYBiQfwXn2.pgp Description: PGP signature
Re: glabel+gmirror (8.0-RC1 problem)
Pawel Jakub Dawidek wrote: Yes. tunefs(8) updates only on-disk super-block, but the kernel holds super-block that was read before. Now when you do 'mount -rw /' the in-kernel super-block is stored to the disk, and there is nothing about your label in there, so it gets overwritten. Ok this sounds familar to me - maybe I have read about this before ;) What would be the prefered way to label the root partition and changing fstab without entering the root partition at bootup manually at least once? Is there a way to do so? I noticed that even when I boot in multiuser, change fstab, then return into single user mode and remount / read-only, the label cannot be set. I need to boot directly into single user mode. Looks like writing the label is denied when the partition was once mounted rw before - even if it is actually mounted ro. -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: glabel+gmirror (8.0-RC1 problem)
Hi, that gmirror together with glabel cannot be used looks like a problem introduced with 8.0-RC1 to me. What I did: 2. Installation 3. reboot 4. mirror Root-hdd sysctl kern.geom.debugflags=17 gmirror label -vb round-robin gm0 da0 gmirror load echo 'geom_mirror_load=YES' /boot/loader.conf echo 'geom_label_load=YES' /boot/loader.conf 5. adjust fstab vi /etc/fstab :%s/ad/mirror\/gm/g 6. reboot 7. mirror Root-hdd gmirror insert gm0 da1 gmirror status 8. wait until gmirror is done 9. reboot 10. glabel status With 8.0-RC1 I see only da0s1a, da0s1d, da0s1e and da0s1f as Components shown by glabel(8). With 8.0-BETA3 I see mirror/gm0s1a, mirror/gm0s1d, mirror/gm0s1e and mirror/gm0s1f as Components which would be correct here. I use old IBM 2GB DFHS harddisks for that tests. I have a bunch of them so I used for both tries fresh drives. I can't see what has changed here between BETA3 and RC1 but something must have changed in a way which renders gmirror together with glabel on RC1 non-working. I just did that as testing the configuration I want to use for my fileserver when the new harddisks arrived but now I'm not sure If I should rely on gmirror+glabel Oliver Lehmann wrote: Hi, I try to glabel (tunefs -L) my gmirror RAID-1. After labeling the /usr, /tmp, /var partition, glabel status shows the labes are being assigned to the mirror/gm0s1* partitions. I then changed my /etc/fstab to use the ufs/label devices instead of the mirror/gm0s1* devices. After the system got rebootet, the system is now unable to mount the partitions and puts me into the single user mode. glabel status shows me now, that the labels are all assigned to da0s1* instead of mirror/gm0s1*. How did this happen? glabel never shows the mirror/gm0s1* partitions anyhow - only after labeling them. But after reboot the labels are reassigned to da0s1* and glabel does not show any mirror/gm0s1* label. How can I prevent this to happen? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
