Re: define more partitions in freebsd
thanks Carl, i tried your your manual step by steps on FreeBSD8.2 but error happened. this is what i've done: gpart create -s MBR ad3 ad3 created gpart add -t freebsd ad3 ad3s1 added gpart create -s BSD -n 20 ad3s1 gpart: geom 'ad3s1': File Exists if i do not run the second command and run the third one, it says invalid argument. i don't know what should i do:( any comments or hints are really appreciated. On Sun, Jun 2, 2013 at 11:31 PM, Carl Johnson ca...@peak.org wrote: s m sam.gh1...@gmail.com writes: thanks guys, i understand another solution is GPT partitioning. but i prefer to have more partitions in traditional freebsd (with MBR table i think). using GPT is the last solution for me. i should create more than 8 partitions with gpart command (flag n which identifies entries) but i have errors when using it. is there any special option which should be included in kernel in order to use gpart with flag n? any one test it before? thanks in advance, I just tried it on a FreeBSD 8.3 system without any problems. You will need to explain what kind of errors you had before anybody can help you. I used a zfs volume for testing as follows: gpart create -s MBR /dev/zvol/zpool/v/gtest gpart add -t freebsd /dev/zvol/zpool/v/gtest gpart create -s BSD -n 20 zvol/zpool/v/gtests1 gpart add -t freebsd-ufs -s 1G zvol/zpool/v/gtests1 gpart add -t freebsd-swap -s 2G zvol/zpool/v/gtests1 # add several more freebsd-ufs # output from 'gpart show zvol/zpool/v/gtests1' = 0 41942943 zvol/zpool/v/gtests1 BSD (20G) 0 2097152 1 freebsd-ufs (1.0G) 2097152 4194304 2 freebsd-swap (2.0G) 6291456 2097152 4 freebsd-ufs (1.0G) 8388608 2097152 5 freebsd-ufs (1.0G) 10485760 2097152 6 freebsd-ufs (1.0G) 12582912 2097152 7 freebsd-ufs (1.0G) 14680064 2097152 8 freebsd-ufs (1.0G) 16777216 2097152 9 freebsd-ufs (1.0G) 18874368 209715210 freebsd-ufs (1.0G) 20971520 209715211 freebsd-ufs (1.0G) 23068672 209715212 freebsd-ufs (1.0G) 25165824 209715213 freebsd-ufs (1.0G) 27262976 209715214 freebsd-ufs (1.0G) 29360128 209715215 freebsd-ufs (1.0G) 31457280 209715216 freebsd-ufs (1.0G) 33554432 209715217 freebsd-ufs (1.0G) 35651584 209715218 freebsd-ufs (1.0G) 37748736 209715219 freebsd-ufs (1.0G) 39845888 209705520 freebsd-ufs (1G) # output from 'disklabel zvol/zpool/v/gtests1' # /dev/zvol/zpool/v/gtests1: 20 partitions: # size offsetfstype [fsize bsize bps/cpg] a:2097152 04.2BSD0 0 0 b:41943042097152 swap c: 41942943 0unused0 0 # raw part, don't edit d:209715262914564.2BSD0 0 0 e:209715283886084.2BSD0 0 0 f:2097152 104857604.2BSD0 0 0 g:2097152 125829124.2BSD0 0 0 h:2097152 146800644.2BSD0 0 0 i:2097152 167772164.2BSD0 0 0 j:2097152 188743684.2BSD0 0 0 k:2097152 209715204.2BSD0 0 0 l:2097152 230686724.2BSD0 0 0 m:2097152 251658244.2BSD0 0 0 n:2097152 272629764.2BSD0 0 0 o:2097152 293601284.2BSD0 0 0 p:2097152 314572804.2BSD0 0 0 q:2097152 335544324.2BSD0 0 0 r:2097152 356515844.2BSD0 0 0 s:2097152 377487364.2BSD0 0 0 t:2097055 398458884.2BSD0 0 0 I also tried newfs on all the ufs partitions without problems. I just tried this on a FreeBSD 8.2 system and it works there as well. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- *Sa.M* ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: define more partitions in freebsd
On Mon, 3 Jun 2013, saeedeh motlagh wrote: thanks Carl, i tried your your manual step by steps on FreeBSD8.2 but error happened. this is what i've done: gpart create -s MBR ad3 ad3 created gpart add -t freebsd ad3 ad3s1 added gpart create -s BSD -n 20 ad3s1 gpart: geom 'ad3s1': File Exists if i do not run the second command and run the third one, it says invalid argument. i don't know what should i do:( any comments or hints are really appreciated. [please stop top-posting, it makes replies more difficult] The slice entry is still present on the disk, and must be removed and recreated: gpart delete -i1 ad3 gpart add -t freebsd ad3 Again, GPT is a better solution unless you have a Thinkpad with a broken BIOS. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: define more partitions in freebsd
On 2013-06-01 08:40, s m wrote: hello all i want to install freebsd8.2 on my system. for some reasons, i need partitions more than 6. my freebsd just allow me to define partitions from a to h, not any more. i checked FreeBSD handbook, but it doesn't say anything about defining more partitions. my question is: how can i define more partitions on my freebsd? (for example, ad3s1a, ..., ad3s1h, ad3s1i, ad3s1j, ...). any comments or hints are appreciated. SAM Put another disk in your machine. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: define more partitions in freebsd
thanks guys, i understand another solution is GPT partitioning. but i prefer to have more partitions in traditional freebsd (with MBR table i think). using GPT is the last solution for me. i should create more than 8 partitions with gpart command (flag n which identifies entries) but i have errors when using it. is there any special option which should be included in kernel in order to use gpart with flag n? any one test it before? thanks in advance, SAM On Sat, Jun 1, 2013 at 8:23 PM, Carl Johnson ca...@peak.org wrote: s m sam.gh1...@gmail.com writes: hello all i want to install freebsd8.2 on my system. for some reasons, i need partitions more than 6. my freebsd just allow me to define partitions from a to h, not any more. i checked FreeBSD handbook, but it doesn't say anything about defining more partitions. my question is: how can i define more partitions on my freebsd? (for example, ad3s1a, ..., ad3s1h, ad3s1i, ad3s1j, ...). any comments or hints are appreciated. SAM Others have already commented that GPT labels are better, but I think that you can have more than 8 partitions. I remember a posting a while back that the maximum had been increased. You will have to experiment if you want to do this, but gpart shows an example that uses 20 partitions: '/sbin/gpart create -s BSD -n 20 ada0s1'. I also don't know that bsdlabel will handle these, so you definitely should experiment first. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: define more partitions in freebsd
On Sun, 2 Jun 2013 11:35:58 +0430 s m wrote: thanks guys, i understand another solution is GPT partitioning. but i prefer to have more partitions in traditional freebsd (with MBR table i think). using GPT is the last solution for me. i should create more than 8 partitions with gpart command (flag n which identifies entries) but i have errors when using it. is there any special option which should be included in kernel in order to use gpart with flag n? any one test it before? IIRC it's possible to label traditional BSD partitions recursively allowing an unlimited number e.g. if you relabel ad0S1f you can have ad0S1fa, ad0S1fb etc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: define more partitions in freebsd
thanks RW, do you have any suggestions how i can do that? with gpart command? On Sun, Jun 2, 2013 at 3:51 PM, RW rwmailli...@googlemail.com wrote: On Sun, 2 Jun 2013 11:35:58 +0430 s m wrote: thanks guys, i understand another solution is GPT partitioning. but i prefer to have more partitions in traditional freebsd (with MBR table i think). using GPT is the last solution for me. i should create more than 8 partitions with gpart command (flag n which identifies entries) but i have errors when using it. is there any special option which should be included in kernel in order to use gpart with flag n? any one test it before? IIRC it's possible to label traditional BSD partitions recursively allowing an unlimited number e.g. if you relabel ad0S1f you can have ad0S1fa, ad0S1fb etc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- *Sa.M* ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: define more partitions in freebsd
s m sam.gh1...@gmail.com writes: thanks guys, i understand another solution is GPT partitioning. but i prefer to have more partitions in traditional freebsd (with MBR table i think). using GPT is the last solution for me. i should create more than 8 partitions with gpart command (flag n which identifies entries) but i have errors when using it. is there any special option which should be included in kernel in order to use gpart with flag n? any one test it before? thanks in advance, I just tried it on a FreeBSD 8.3 system without any problems. You will need to explain what kind of errors you had before anybody can help you. I used a zfs volume for testing as follows: gpart create -s MBR /dev/zvol/zpool/v/gtest gpart add -t freebsd /dev/zvol/zpool/v/gtest gpart create -s BSD -n 20 zvol/zpool/v/gtests1 gpart add -t freebsd-ufs -s 1G zvol/zpool/v/gtests1 gpart add -t freebsd-swap -s 2G zvol/zpool/v/gtests1 # add several more freebsd-ufs # output from 'gpart show zvol/zpool/v/gtests1' = 0 41942943 zvol/zpool/v/gtests1 BSD (20G) 0 2097152 1 freebsd-ufs (1.0G) 2097152 4194304 2 freebsd-swap (2.0G) 6291456 2097152 4 freebsd-ufs (1.0G) 8388608 2097152 5 freebsd-ufs (1.0G) 10485760 2097152 6 freebsd-ufs (1.0G) 12582912 2097152 7 freebsd-ufs (1.0G) 14680064 2097152 8 freebsd-ufs (1.0G) 16777216 2097152 9 freebsd-ufs (1.0G) 18874368 209715210 freebsd-ufs (1.0G) 20971520 209715211 freebsd-ufs (1.0G) 23068672 209715212 freebsd-ufs (1.0G) 25165824 209715213 freebsd-ufs (1.0G) 27262976 209715214 freebsd-ufs (1.0G) 29360128 209715215 freebsd-ufs (1.0G) 31457280 209715216 freebsd-ufs (1.0G) 33554432 209715217 freebsd-ufs (1.0G) 35651584 209715218 freebsd-ufs (1.0G) 37748736 209715219 freebsd-ufs (1.0G) 39845888 209705520 freebsd-ufs (1G) # output from 'disklabel zvol/zpool/v/gtests1' # /dev/zvol/zpool/v/gtests1: 20 partitions: # size offsetfstype [fsize bsize bps/cpg] a:2097152 04.2BSD0 0 0 b:41943042097152 swap c: 41942943 0unused0 0 # raw part, don't edit d:209715262914564.2BSD0 0 0 e:209715283886084.2BSD0 0 0 f:2097152 104857604.2BSD0 0 0 g:2097152 125829124.2BSD0 0 0 h:2097152 146800644.2BSD0 0 0 i:2097152 167772164.2BSD0 0 0 j:2097152 188743684.2BSD0 0 0 k:2097152 209715204.2BSD0 0 0 l:2097152 230686724.2BSD0 0 0 m:2097152 251658244.2BSD0 0 0 n:2097152 272629764.2BSD0 0 0 o:2097152 293601284.2BSD0 0 0 p:2097152 314572804.2BSD0 0 0 q:2097152 335544324.2BSD0 0 0 r:2097152 356515844.2BSD0 0 0 s:2097152 377487364.2BSD0 0 0 t:2097055 398458884.2BSD0 0 0 I also tried newfs on all the ufs partitions without problems. I just tried this on a FreeBSD 8.2 system and it works there as well. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
define more partitions in freebsd
hello all i want to install freebsd8.2 on my system. for some reasons, i need partitions more than 6. my freebsd just allow me to define partitions from a to h, not any more. i checked FreeBSD handbook, but it doesn't say anything about defining more partitions. my question is: how can i define more partitions on my freebsd? (for example, ad3s1a, ..., ad3s1h, ad3s1i, ad3s1j, ...). any comments or hints are appreciated. SAM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: define more partitions in freebsd
On Sat, 1 Jun 2013 11:10:32 +0430, s m wrote: hello all i want to install freebsd8.2 on my system. for some reasons, i need partitions more than 6. my freebsd just allow me to define partitions from a to h, not any more. That's correct and expected for the MBR partitioning approach (which is considered mostly outdated today). i checked FreeBSD handbook, but it doesn't say anything about defining more partitions. Because you _cannot_ define more partitions than up to 'h'. This is a hard-defined limit of MBR-style partitions (as they are initialized with bsdlabel). my question is: how can i define more partitions on my freebsd? (for example, ad3s1a, ..., ad3s1h, ad3s1i, ad3s1j, ...). You cannot. You need to use the GPT partitioning approach and repartition your disk. With gpart, you can create more than 'h' partitions, but the partitions will have different names, such as ad3s1p1, ad3s1p2, ..., ad3s1p10, ad3s1p11, ... and so on. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: define more partitions in freebsd
thanks for your reply, it is a good news if i can define more partitions with gpart. names are not so important for me. if i can define more partitions with gpart, are these partitions work correctly? you know i wan to define a journal partition for each partition on my freebsd. so if i use these extra partition as journal provider, do they work correctly? and another question, how can i define more partitions with gpart? i searched and some people say to use gpart -n 20. do you mean to use this command too? and my last question, some people say to change byte 0x28a of the disk from 0x08 to 0x14 (which 14 is the number of partitions). do you think it's a good idea and applicable solution? thanks for your attention On 6/1/13, Polytropon free...@edvax.de wrote: On Sat, 1 Jun 2013 11:10:32 +0430, s m wrote: hello all i want to install freebsd8.2 on my system. for some reasons, i need partitions more than 6. my freebsd just allow me to define partitions from a to h, not any more. That's correct and expected for the MBR partitioning approach (which is considered mostly outdated today). i checked FreeBSD handbook, but it doesn't say anything about defining more partitions. Because you _cannot_ define more partitions than up to 'h'. This is a hard-defined limit of MBR-style partitions (as they are initialized with bsdlabel). my question is: how can i define more partitions on my freebsd? (for example, ad3s1a, ..., ad3s1h, ad3s1i, ad3s1j, ...). You cannot. You need to use the GPT partitioning approach and repartition your disk. With gpart, you can create more than 'h' partitions, but the partitions will have different names, such as ad3s1p1, ad3s1p2, ..., ad3s1p10, ad3s1p11, ... and so on. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: define more partitions in freebsd
s m writes: and my last question, some people say to change byte 0x28a of the disk from 0x08 to 0x14 (which 14 is the number of partitions). do you think it's a good idea and applicable solution? Short answer: if you have to ask - no, it isn't. :-) Respectfully, Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: define more partitions in freebsd
thanks Robert, so i just have one choice: gpart. do you know how to use it? i define ad3 and ad3s1; after that i run this command: gpart create -s mbr -n 20 ad3s1. but this error happens: GEOM: file exists. after that i do it again in different way: i create ad3 and after that run the above command but it says: invalid argument ad3s1. i think because there is no ad3s1!!! now how can i use -n flag to set entries number for my partitioning??? you know it is so important for me :(( any comments or hints are really appreciated. SAM On 6/1/13, Robert Huff roberth...@rcn.com wrote: s m writes: and my last question, some people say to change byte 0x28a of the disk from 0x08 to 0x14 (which 14 is the number of partitions). do you think it's a good idea and applicable solution? Short answer: if you have to ask - no, it isn't. :-) Respectfully, Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: define more partitions in freebsd
On Sat, 1 Jun 2013 11:10:32 +0430, s m wrote: hello all i want to install freebsd8.2 on my system. for some reasons, i need partitions more than 6. my freebsd just allow me to define partitions from a to h, not any more. That's correct and expected for the MBR partitioning approach (which is considered mostly outdated today). i checked FreeBSD handbook, but it doesn't say anything about defining more partitions. Because you _cannot_ define more partitions than up to 'h'. This is a hard-defined limit of MBR-style partitions (as they are initialized with bsdlabel). my question is: how can i define more partitions on my freebsd? (for example, ad3s1a, ..., ad3s1h, ad3s1i, ad3s1j, ...). You cannot. You need to use the GPT partitioning approach and repartition your disk. With gpart, you can create more than 'h' partitions, but the partitions will have different names, such as ad3s1p1, ad3s1p2, ..., ad3s1p10, ad3s1p11, ... and so on. Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... Are you sure of this? Can you GPT-partition an MBR slice as opposed to the whole disk? You should get ad3p1, ad3p2, ...,ad3p10, ad3p11, ... Then you would have to migrate an MBR partition table to GPT, if you have non-FreeBSD slices. I don't know if gpart can do that, but Rod Smith's gdisk (included in FreeBSD ports) or gpt (still used in NetBSD but not FreeBSD) can. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: define more partitions in freebsd
On Sat, 1 Jun 2013, Polytropon wrote: On Sat, 1 Jun 2013 11:10:32 +0430, s m wrote: my question is: how can i define more partitions on my freebsd? (for example, ad3s1a, ..., ad3s1h, ad3s1i, ad3s1j, ...). You cannot. You need to use the GPT partitioning approach and repartition your disk. With gpart, you can create more than 'h' partitions, but the partitions will have different names, such as ad3s1p1, ad3s1p2, ..., ad3s1p10, ad3s1p11, ... and so on. GPT partitioning is a replacement for MBR partitioning, and will generally look like ad3p1, ad3p2, and so on. FreeBSD's GPT implementation should allow 128 GPT partitions by default, although I have not tested that. Use of gpart to set up a disk is shown here: http://www.wonkity.com/~wblock/docs/html/disksetup.html The FreeBSD 9.x installer, bsdinstall, uses GPT partitioning by default. The older sysinstall that is used on FreeBSD 8 does not, and probably has no native way to use GPT. The partitions would have to be set up manually from a shell before running the installer, and then manually entered in the installer. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: define more partitions in freebsd
On Sat, 1 Jun 2013 07:10:03 -0600 (MDT), Warren Block wrote: On Sat, 1 Jun 2013, Polytropon wrote: On Sat, 1 Jun 2013 11:10:32 +0430, s m wrote: my question is: how can i define more partitions on my freebsd? (for example, ad3s1a, ..., ad3s1h, ad3s1i, ad3s1j, ...). You cannot. You need to use the GPT partitioning approach and repartition your disk. With gpart, you can create more than 'h' partitions, but the partitions will have different names, such as ad3s1p1, ad3s1p2, ..., ad3s1p10, ad3s1p11, ... and so on. GPT partitioning is a replacement for MBR partitioning, and will generally look like ad3p1, ad3p2, and so on. Sorry for my inaccuracy: Of course the slicing part as well as the BSD partitions are _both_ replaced by GPT partition numbers. Use of gpart to set up a disk is shown here: http://www.wonkity.com/~wblock/docs/html/disksetup.html That article should be on the top of each list regarding disk partitioning on FreeBSD, maybe something comparable could be added to the Handbook? The FreeBSD 9.x installer, bsdinstall, uses GPT partitioning by default. The older sysinstall that is used on FreeBSD 8 does not, and probably has no native way to use GPT. As far as I know: no. You have to use the common CLI tools if you want to install FreeBSD 8 on a GPT system (but it's easily possible). The partitions would have to be set up manually from a shell before running the installer, and then manually entered in the installer. With the precaution of _not_ to vary existing partitions. However, I don't know how the installer will handle the non-MBR partitions (probably comparable to dedicated partitions?), I've never tried that. (Even for dedicated layout, I personally tend to use CLI only, without using sysinstall or sade). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: define more partitions in freebsd
On Sat, 1 Jun 2013 05:36:13 -0700 (PDT), Thomas Mueller wrote: On Sat, 1 Jun 2013 11:10:32 +0430, s m wrote: hello all i want to install freebsd8.2 on my system. for some reasons, i need partitions more than 6. my freebsd just allow me to define partitions from a to h, not any more. That's correct and expected for the MBR partitioning approach (which is considered mostly outdated today). i checked FreeBSD handbook, but it doesn't say anything about defining more partitions. Because you _cannot_ define more partitions than up to 'h'. This is a hard-defined limit of MBR-style partitions (as they are initialized with bsdlabel). my question is: how can i define more partitions on my freebsd? (for example, ad3s1a, ..., ad3s1h, ad3s1i, ad3s1j, ...). You cannot. You need to use the GPT partitioning approach and repartition your disk. With gpart, you can create more than 'h' partitions, but the partitions will have different names, such as ad3s1p1, ad3s1p2, ..., ad3s1p10, ad3s1p11, ... and so on. Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... Are you sure of this? Can you GPT-partition an MBR slice as opposed to the whole disk? Probably not. GPT obsoletes both slices and partitions. You should get ad3p1, ad3p2, ...,ad3p10, ad3p11, ... That is what I should have written. :-) Then you would have to migrate an MBR partition table to GPT, if you have non-FreeBSD slices. I don't know if gpart can do that, but Rod Smith's gdisk (included in FreeBSD ports) or gpt (still used in NetBSD but not FreeBSD) can. The simplest approach would probably be to backup the data from the existing partitions, re-inialize the whole disk with a GPT scheme, format the (GPT) partitions and then restore the dump previously taken. I'm not sure if such kind of harsh re-partitioning can be done _safely_ on the fly... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: define more partitions in freebsd
s m sam.gh1...@gmail.com writes: hello all i want to install freebsd8.2 on my system. for some reasons, i need partitions more than 6. my freebsd just allow me to define partitions from a to h, not any more. i checked FreeBSD handbook, but it doesn't say anything about defining more partitions. my question is: how can i define more partitions on my freebsd? (for example, ad3s1a, ..., ad3s1h, ad3s1i, ad3s1j, ...). any comments or hints are appreciated. SAM Others have already commented that GPT labels are better, but I think that you can have more than 8 partitions. I remember a posting a while back that the maximum had been increased. You will have to experiment if you want to do this, but gpart shows an example that uses 20 partitions: '/sbin/gpart create -s BSD -n 20 ada0s1'. I also don't know that bsdlabel will handle these, so you definitely should experiment first. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mount Logical (ext2fs) Partitions?
On Fri, 25 Jan 2013 21:07:59 -0800, Carl Johnson wrote: There is a package called 'linuxfdisk' that is just a FreeBSD implementation of the linux fdisk and will show you what the FreeBSD partitions/slices are. You can also use gpart in the base system to get the same information. The command 'gpart list ada0' will show the primary partitions, and the command 'gpart list ada0s4' should show the logical partitions inside of the extended partition. You can also use 'file -s' and possibly do read-only mounts to see exactly what they contain. The names will probably map out like linux, but the 'sda*' will be changed to 'ada0s*'. Thanks for the pointers. Here is the relevant part of the output from 'gpart list ada0s4': 4. Name: ada0s8 Mediasize: 4194304 (39G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 162529280 Mode: r0w0e0 rawtype: 131 length: 4194304 offset: 46143188992 type: linux-data index: 1430498 end: 172043415 start: 90121368 So I put into my /etc/fstab: /dev/ada0s8 /u01ext2fs ro,noauto 00 But when I issue 'sudo mount /u01' I get: mount: /dev/ada0s8: Invalid argument What am I doing wrong? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mount Logical (ext2fs) Partitions?
Walter Hurry walterhu...@gmail.com writes: On Fri, 25 Jan 2013 21:07:59 -0800, Carl Johnson wrote: There is a package called 'linuxfdisk' that is just a FreeBSD implementation of the linux fdisk and will show you what the FreeBSD partitions/slices are. You can also use gpart in the base system to get the same information. The command 'gpart list ada0' will show the primary partitions, and the command 'gpart list ada0s4' should show the logical partitions inside of the extended partition. You can also use 'file -s' and possibly do read-only mounts to see exactly what they contain. The names will probably map out like linux, but the 'sda*' will be changed to 'ada0s*'. Thanks for the pointers. Here is the relevant part of the output from 'gpart list ada0s4': 4. Name: ada0s8 Mediasize: 4194304 (39G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 162529280 Mode: r0w0e0 rawtype: 131 length: 4194304 offset: 46143188992 type: linux-data index: 1430498 end: 172043415 start: 90121368 So I put into my /etc/fstab: /dev/ada0s8 /u01ext2fs ro,noauto 00 But when I issue 'sudo mount /u01' I get: mount: /dev/ada0s8: Invalid argument What am I doing wrong? I don't see anything wrong there. I use labels when possible, but that doesn't really change anything. Have you tried using 'file -s /dev/ada0s8' to see what the kernel thinks it is? -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mount Logical (ext2fs) Partitions?
On Sat, 26 Jan 2013 18:24:06 +0100, Carl Johnson ca...@peak.org wrote: /dev/ada0s8 /u01ext2fs ro,noauto 00 I've got 2 ext3 partitions mounted. /dev/ada0s8 /mnt/dump ext2fs rw 0 0 /dev/ada0s9 /mnt/archlinux ext2fs rw 0 0 Did you already test rw? Even if you wish ro,..., just for testing purpose. $ uname -a FreeBSD freebsd 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Regards, Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mount Logical (ext2fs) Partitions?
On Sat, 26 Jan 2013 09:24:06 -0800, Carl Johnson wrote: Walter Hurry walterhu...@gmail.com writes: On Fri, 25 Jan 2013 21:07:59 -0800, Carl Johnson wrote: There is a package called 'linuxfdisk' that is just a FreeBSD implementation of the linux fdisk and will show you what the FreeBSD partitions/slices are. You can also use gpart in the base system to get the same information. The command 'gpart list ada0' will show the primary partitions, and the command 'gpart list ada0s4' should show the logical partitions inside of the extended partition. You can also use 'file -s' and possibly do read-only mounts to see exactly what they contain. The names will probably map out like linux, but the 'sda*' will be changed to 'ada0s*'. Thanks for the pointers. Here is the relevant part of the output from 'gpart list ada0s4': 4. Name: ada0s8 Mediasize: 4194304 (39G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 162529280 Mode: r0w0e0 rawtype: 131 length: 4194304 offset: 46143188992 type: linux-data index: 1430498 end: 172043415 start: 90121368 So I put into my /etc/fstab: /dev/ada0s8 /u01ext2fs ro,noauto 0 0 But when I issue 'sudo mount /u01' I get: mount: /dev/ada0s8: Invalid argument What am I doing wrong? I don't see anything wrong there. I use labels when possible, but that doesn't really change anything. Have you tried using 'file -s /dev/ada0s8' to see what the kernel thinks it is? Sorry, I didn't take advantage of that earlier piece of advice. Here it is: $ file -s /dev/ada0s8 /dev/ada0s8: no read permission $ ls -l /dev/ada0s8 crw-r- 1 root operator0, 102 26 Jan 18:09 / dev/ada0s8 $ sudo file -s /dev/ada0s8 /dev/ada0s8: Linux rev 1.0 ext4 filesystem data,UUID=d93b0074-04ca-4e5d-bee9-dfd85bce0b14, volume name u01 (extents) (large files) (huge files) $ So it's my stupid mistake. I could have sworn it was ext2, but it was ext4. Sorry for all the noise! However, I'm glad you have helped, and that I have learned a little bit about Linux partitions as FreeeBSD slices. It was empty, so I just reformatted it as ext2, and hey presto; all is right with the world. Thanks again. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mount Logical (ext2fs) Partitions?
Walter Hurry walterhu...@gmail.com writes: So it's my stupid mistake. I could have sworn it was ext2, but it was ext4. Sorry for all the noise! However, I'm glad you have helped, and that I have learned a little bit about Linux partitions as FreeeBSD slices. It was empty, so I just reformatted it as ext2, and hey presto; all is right with the world. Good to know you have it working, but for future reference there is a fuse implementation of an ext4 driver: sysutils/fusefs-ext4fuse EXT4 implementation for FUSE EXT4 implementation for FUSE. WWW: https://github.com/gerard/ext4fuse/ I haven't tried it so I don't know how well it works. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mount Logical (ext2fs) Partitions?
On Sat, 26 Jan 2013 14:43:51 -0800, Carl Johnson wrote: Walter Hurry walterhu...@gmail.com writes: So it's my stupid mistake. I could have sworn it was ext2, but it was ext4. Sorry for all the noise! However, I'm glad you have helped, and that I have learned a little bit about Linux partitions as FreeeBSD slices. It was empty, so I just reformatted it as ext2, and hey presto; all is right with the world. Good to know you have it working, but for future reference there is a fuse implementation of an ext4 driver: sysutils/fusefs-ext4fuse EXT4 implementation for FUSE EXT4 implementation for FUSE. WWW: https://github.com/gerard/ext4fuse/ I haven't tried it so I don't know how well it works. Even better! But I'll leave it for the moment; ext2 will suffice for my simple requirements (I only want to share a few files between FreeBSD and Linux without the overhead of putting them onto the external USB drive which I use for backups). I have of course mounted them rw, now that it's working. Many thanks once again. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Mount Logical (ext2fs) Partitions?
9.1 on x86_64. No doubt this question has been asked before, but how do I mount logical partitions (e2fs) under FreeBSD? I have checked the handbook, and DuckDuckGo'ed, but without finding anything useful. The third slice on my first disk is a physical one, and will mount happily under FreeBSD. From /etc/fstab: /dev/ada0s3 /Mail ext2fs rw00 But I have a couple of logical partitions (also ext2fs) in the fourth slice, which I have been trying, unsuccessfully, to mount. For information, here is the BSD view of the disk: $ sudo fdisk *** Working on device /dev/ada0 *** parameters extracted from in-core disklabel are: cylinders=310101 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=310101 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 131 (0x83),(Linux native) start 2048, size 24576000 (12000 Meg), flag 0 beg: cyl 0/ head 32/ sector 33; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 24578064, size 44040150 (21503 Meg), flag 80 (active) beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 255/ sector 63 The data for partition 3 is: sysid 131 (0x83),(Linux native) start 68618240, size 958464 (468 Meg), flag 0 beg: cyl 1023/ head 254/ sector 63; end: cyl 1023/ head 254/ sector 63 The data for partition 4 is: sysid 5 (0x05),(Extended DOS) start 69577576, size 243002520 (118653 Meg), flag 0 beg: cyl 1023/ head 254/ sector 63; end: cyl 1023/ head 254/ sector 63 $ Now here's how Linux sees it: $ sudo fdisk -l /dev/sda Disk /dev/sda: 160.0 GB, 160041885696 bytes, 312581808 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x38d5b517 Device Boot Start End Blocks Id System /dev/sda120482457804712288000 83 Linux /dev/sda2 *245780646861821322020075 a5 FreeBSD /dev/sda36861824069576703 479232 83 Linux /dev/sda469577576 312580095 1215012605 Extended /dev/sda594158848 112590847 9216000 83 Linux /dev/sda6 112592896 118736895 3072000 82 Linux swap / Solaris /dev/sda7 118738944 1596989432048 83 Linux /dev/sda8 159700992 2416209914096 83 Linux /dev/sda9 241623040 27029913514338048 83 Linux /dev/sda10 270301184 31258009521139456 83 Linux /dev/sda11 695808009415679912288000 83 Linux Partition table entries are not in disk order $ Can anyone provide a pointer please? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mount Logical (ext2fs) Partitions?
On 1/25/2013 5:36 PM, Walter Hurry wrote: 9.1 on x86_64. No doubt this question has been asked before, but how do I mount logical partitions (e2fs) under FreeBSD? I have checked the handbook, and DuckDuckGo'ed, but without finding anything useful. The third slice on my first disk is a physical one, and will mount happily under FreeBSD. From /etc/fstab: /dev/ada0s3 /Mail ext2fs rw00 But I have a couple of logical partitions (also ext2fs) in the fourth slice, which I have been trying, unsuccessfully, to mount. For information, here is the BSD view of the disk: $ sudo fdisk *** Working on device /dev/ada0 *** parameters extracted from in-core disklabel are: cylinders=310101 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=310101 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 131 (0x83),(Linux native) start 2048, size 24576000 (12000 Meg), flag 0 beg: cyl 0/ head 32/ sector 33; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 24578064, size 44040150 (21503 Meg), flag 80 (active) beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 255/ sector 63 The data for partition 3 is: sysid 131 (0x83),(Linux native) start 68618240, size 958464 (468 Meg), flag 0 beg: cyl 1023/ head 254/ sector 63; end: cyl 1023/ head 254/ sector 63 The data for partition 4 is: sysid 5 (0x05),(Extended DOS) start 69577576, size 243002520 (118653 Meg), flag 0 beg: cyl 1023/ head 254/ sector 63; end: cyl 1023/ head 254/ sector 63 $ Now here's how Linux sees it: $ sudo fdisk -l /dev/sda Disk /dev/sda: 160.0 GB, 160041885696 bytes, 312581808 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x38d5b517 Device Boot Start End Blocks Id System /dev/sda120482457804712288000 83 Linux /dev/sda2 *245780646861821322020075 a5 FreeBSD /dev/sda36861824069576703 479232 83 Linux /dev/sda469577576 312580095 1215012605 Extended /dev/sda594158848 112590847 9216000 83 Linux /dev/sda6 112592896 118736895 3072000 82 Linux swap / Solaris /dev/sda7 118738944 1596989432048 83 Linux /dev/sda8 159700992 2416209914096 83 Linux /dev/sda9 241623040 27029913514338048 83 Linux /dev/sda10 270301184 31258009521139456 83 Linux /dev/sda11 695808009415679912288000 83 Linux Partition table entries are not in disk order $ Can anyone provide a pointer please? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org What do /dev and the output of dmesg look like? It looks like linux fdisk is hiding the fact that you have to cheat the bios to get more than four partitions with MBR partitioning. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mount Logical (ext2fs) Partitions?
Walter Hurry walterhu...@gmail.com writes: 9.1 on x86_64. No doubt this question has been asked before, but how do I mount logical partitions (e2fs) under FreeBSD? I have checked the handbook, and DuckDuckGo'ed, but without finding anything useful. The third slice on my first disk is a physical one, and will mount happily under FreeBSD. From /etc/fstab: /dev/ada0s3 /Mail ext2fs rw00 But I have a couple of logical partitions (also ext2fs) in the fourth slice, which I have been trying, unsuccessfully, to mount. For information, here is the BSD view of the disk: $ sudo fdisk *** Working on device /dev/ada0 *** parameters extracted from in-core disklabel are: cylinders=310101 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=310101 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 131 (0x83),(Linux native) start 2048, size 24576000 (12000 Meg), flag 0 beg: cyl 0/ head 32/ sector 33; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 24578064, size 44040150 (21503 Meg), flag 80 (active) beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 255/ sector 63 The data for partition 3 is: sysid 131 (0x83),(Linux native) start 68618240, size 958464 (468 Meg), flag 0 beg: cyl 1023/ head 254/ sector 63; end: cyl 1023/ head 254/ sector 63 The data for partition 4 is: sysid 5 (0x05),(Extended DOS) start 69577576, size 243002520 (118653 Meg), flag 0 beg: cyl 1023/ head 254/ sector 63; end: cyl 1023/ head 254/ sector 63 $ Now here's how Linux sees it: $ sudo fdisk -l /dev/sda Disk /dev/sda: 160.0 GB, 160041885696 bytes, 312581808 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x38d5b517 Device Boot Start End Blocks Id System /dev/sda120482457804712288000 83 Linux /dev/sda2 *245780646861821322020075 a5 FreeBSD /dev/sda36861824069576703 479232 83 Linux /dev/sda469577576 312580095 1215012605 Extended /dev/sda594158848 112590847 9216000 83 Linux /dev/sda6 112592896 118736895 3072000 82 Linux swap / Solaris /dev/sda7 118738944 1596989432048 83 Linux /dev/sda8 159700992 2416209914096 83 Linux /dev/sda9 241623040 27029913514338048 83 Linux /dev/sda10 270301184 31258009521139456 83 Linux /dev/sda11 695808009415679912288000 83 Linux There is a package called 'linuxfdisk' that is just a FreeBSD implementation of the linux fdisk and will show you what the FreeBSD partitions/slices are. You can also use gpart in the base system to get the same information. The command 'gpart list ada0' will show the primary partitions, and the command 'gpart list ada0s4' should show the logical partitions inside of the extended partition. You can also use 'file -s' and possibly do read-only mounts to see exactly what they contain. The names will probably map out like linux, but the 'sda*' will be changed to 'ada0s*'. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: bsdinstall misaligns partitions
Christian Weisgerber wrote: Shouldn't bsdinstall attempt to align partitions on 4k boundaries both for the benefit of 4k drives and flash storage? I just installed 9.1R i386 for fun and practice, in fact I installed it several times, and I played around with the partitioning options. * The modern GPT scheme reserves 34 sectors at the start of the disk. Your newly created partitions will start at offset 34 and will therefor be misaligned. I ended up configuring a 63 kB freebsd-boot partition, which ensures that the following partitions are aligned. * The old MBR scheme is even worse. The FreeBSD slice will start at sector 63, guaranteeing that any partitions contained within will be misaligned. There is no way to fix this, unless you shell out and run fdisk manually. * Funnily enough, the ancient BSD dangerously dedicated scheme is the only one that out of the box does not misalign partitions. I'm presumably not the first one to notice this issue, and yes, I'm mostly just venting. Best advice is go submit a pr on this bsdinstall situation. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
bsdinstall misaligns partitions
Shouldn't bsdinstall attempt to align partitions on 4k boundaries both for the benefit of 4k drives and flash storage? I just installed 9.1R i386 for fun and practice, in fact I installed it several times, and I played around with the partitioning options. * The modern GPT scheme reserves 34 sectors at the start of the disk. Your newly created partitions will start at offset 34 and will therefor be misaligned. I ended up configuring a 63 kB freebsd-boot partition, which ensures that the following partitions are aligned. * The old MBR scheme is even worse. The FreeBSD slice will start at sector 63, guaranteeing that any partitions contained within will be misaligned. There is no way to fix this, unless you shell out and run fdisk manually. * Funnily enough, the ancient BSD dangerously dedicated scheme is the only one that out of the box does not misalign partitions. I'm presumably not the first one to notice this issue, and yes, I'm mostly just venting. -- Christian naddy Weisgerber na...@mips.inka.de ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: bsdinstall misaligns partitions
On Fri, Jan 4, 2013 at 9:14 AM, Christian Weisgerber na...@mips.inka.dewrote: Shouldn't bsdinstall attempt to align partitions on 4k boundaries both for the benefit of 4k drives and flash storage? That's rather up to you. AFAIK it attempts to create partitions that preserve cylinder boundaries - which are generally a rather obsolete concept, even for drives with spindles. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: bsdinstall misaligns partitions
On Fri, 4 Jan 2013, Christian Weisgerber wrote: Shouldn't bsdinstall attempt to align partitions on 4k boundaries both for the benefit of 4k drives and flash storage? I think the latest version does. I just installed 9.1R i386 for fun and practice, in fact I installed it several times, and I played around with the partitioning options. * The modern GPT scheme reserves 34 sectors at the start of the disk. Your newly created partitions will start at offset 34 and will therefor be misaligned. I ended up configuring a 63 kB freebsd-boot partition, which ensures that the following partitions are aligned. * The old MBR scheme is even worse. The FreeBSD slice will start at sector 63, guaranteeing that any partitions contained within will be misaligned. There is no way to fix this, unless you shell out and run fdisk manually. Even worse news: you can't fix it manually. Both fdisk and gpart are slaves to the kernel code that deals with MBR layouts, and will align to the old CHS values. I have not found a way to use FreeBSD to create an MBR slice that starts at 1M, block 2048. The CHS alignment always forces it to block 2079, a multiple of 63. However, gpart's -a alignment flag will offset BSD partitions within the slice so they are aligned. * Funnily enough, the ancient BSD dangerously dedicated scheme is the only one that out of the box does not misalign partitions. The filesystems don't begin at the start of the slice anyway. There is a bsdlabel there. I'm presumably not the first one to notice this issue, and yes, I'm mostly just venting. A way to override the CHS alignment would be welcome. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: bsdinstall misaligns partitions
Warren Block: * Funnily enough, the ancient BSD dangerously dedicated scheme is the only one that out of the box does not misalign partitions. The filesystems don't begin at the start of the slice anyway. There is a bsdlabel there. Yes and no. If you look at the bsdlabel(8) output, the size of 'c' is exactly the same as the sum of the sizes of the other partitions, as well as exactly the size of the fdisk slice. There is no additional reserved space for the label. So where does the disklabel hide? FFS1 (FFS2) leaves 8 kB (64 kB) of space at the start of _every_ filesystem. The first 8 kB of the slice--overlapping with the start of 'c' and the start of 'a'--hold boot1, the disklabel, and boot2. If you hexdump /boot/boot2, you'll notice that the first 0x114 bytes are zeroed out; those 276 bytes are exactly where the disklabel is located on disk. See sys/disklabel.h and ufs/ffs/fs.h. -- Christian naddy Weisgerber na...@mips.inka.de ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Groupping restored partitions into slices
Short version: Is it possible to group existing partitions into slices without affecting data? Long version: I had a disk sliced/partitioned like this: ad4s1 ad4s1a ad4s1b (swap) ad4s1d ad4s1e ad4s1f ad4s2 (storage) ad4s3 ad4s3a ad4s3b (swap) ad4s3d ad4s3e ad4s3f Then, I accidentally deleted *something* (wrong use of boot0cfg), which left me with /dev/ad4 only! scan_ffs correctly detected where all 9 data partitions begin. I created new bsdlabel table, wrote it to ad4, so I now have ad4a (former ad4s1a) ad4b (former ad4s1b - swap) ad4d (former ad4s1d) ad4e (former ad4s1e) ad4f (former ad4s1f) ad4g (former ad4s2) ad4h (former ad4s3a) and beginning sectors of the rest (former ad4s3d-f). Of course, I can't make more than 8 labels. I can mount all of them and I see my data. I can even 'swapon ad4b'. Now, the question: how can I restore s1, s2 and s3? As you can guess, s1 and s3 were working systems. Processing all this from FreeBSD-8/amd64 on another disc. Thanks! Sergi M For FreeBSD as opposed to NetBSD, and I believe, OpenBSD, disklabels/bsdlabels are for the slice rather than the whole disk, unless you partition the disk in dangerously dedicated mode. So you should create one bsdlabel for ad4s1 and install to the beginning of that partition, and ahother bsdlabel for ad4s3 and install to the beginning of ad4s3. Installation would be using bsdlabel. That's what I think, I could possibly be wrong. You can check the bsdlabel man page, accessible online from www.freebsd.org, even if you have no working installation of FreeBSD. One, or actually twice, NetBSD overwrote my FreeBSD disklabel/bsdlabel. The first time, I lost my FreeBSD installation but had nothing really to save, it was time to upgrade to FreeBSD 8.0. The second time, I had much software installed, but had the bsdlabel information saved in a file. I booted a FreeBSD rescue CD and restored the FreeBSD disklabel/bsdlabel, and was back in business. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Groupping restored partitions into slices
Thomas, thank you for reply! No, it wasn't dangerously dedicated disk. However, what is the exact command to add ad4s1 and ad4s3 using bsdlabel? Is it possible at all? I thought I should use fdisk or gpart for that. Thanks, Sergi M ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Groupping restored partitions into slices
Thomas, thank you for reply! No, it wasn't dangerously dedicated disk. However, what is the exact command to add ad4s1 and ad4s3 using bsdlabel? Is it possible at all? I thought I should use fdisk or gpart for that. Thanks, Sergi M You use fdisk to create what FreeBSD calls slices such as ad4s1, ad4s2, ad4s3 and disklabel to subdivide a slice into FreeBSD partitions such as ad4s1a, ad4s1b, ad4s1c, etc. gpart is used to create GPT partitions such as ad4p1, ad4p2, ad4p3, etc. Subdividing a slice into FreeBSD partitions is used with MBR partition/slice table but not recommended with GPT. The online FreeBSD bsdlabel man page is online at http://www.freebsd.org/cgi/man.cgi?query=bsdlabelapropos=0sektion=0manpath=FreeBSD+9.0-RELEASEarch=defaultformat=html One example given is This is an example disk label that uses some of the new partition size types such as %, M, G, and *, which could be used as a source file for ``bsdlabel -R ad0s1 new_label_file'': # /dev/ad0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 400M 164.2BSD 4096 1638475 # (Cyl.0 - 812*) b: 1G* swap c: **unused e: 204800*4.2BSD f: 5g*4.2BSD g: **4.2BSD but you would have to replace the * with actual appropriate numbers. After you install the disklabel, you could mount each data partition, but not the swap partition, to see if the directory and file structure looks right. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Groupping restored partitions into slices
Thomas, thank you very much for your mail, but that isn't what I asked. Of course, I know that bsdlabel -R ad0s1 new_label_file writes new labels to ad0s1. My question is: what to do if I _lost_ s1, s2, and s3 - how to recover _them_ first? Without that, all I can do is to write labels table directly on ad0. SergiM. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Groupping restored partitions into slices
Thomas, thank you very much for your mail, but that isn't what I asked. Of course, I know that bsdlabel -R ad0s1 new_label_file writes new labels to ad0s1. My question is: what to do if I _lost_ s1, s2, and s3 - how to recover _them_ first? Without that, all I can do is to write labels table directly on ad0. SergiM. I thought you had found where the slices and partitions had been. Otherwise, if you only have the BSD partitions and need to label more than 8, there is gpart in FreeBSD base system and Rod Smith's gdisk, available in FreeBSD ports and also on the System Rescue CD (sysresccd.org). If you switch to GPT, you can accommodate 128 partitions by default, and you wouldn't need the original slices, just the BSD partitions in what had been the slices. If you switch to GPT as opposed to MBR, you won't use bsdlabel; partitions for each FreeBSD installation would be listed in /etc/fstab. If you have the data, where each slice began and ended, you can restore the slices with fdisk. If you can find the BSD partitions and have the media space to backup to, you might want to backup the partitions if feasible, as protection in case you mess up. NetBSD disklabel can accommodate up to 16 partitions per hard disk, but FreeBSD might not be able to properly read a NetBSD disklabel. Also, NetBSD disklabel is very tricky and temperamental; I'd surely trust gdisk or gpart over NetBSD disklabel. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
reverse label lookup for GPT partitions
'gpart show -l ad4' shows GPT labels on all the ad4 partitions. Is there a reverse lookup, say to find out the GPT label for ad4p4? Yes, it can be parsed out of 'gpart show -l' output, but anything more direct? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can gpart create ntfs and FAT-32 partitions?
On 7/28/2011 7:55 AM, Kevin Oberman wrote:
I want to create a GPT disk structure that has the following partitions:
MBR
NTFS (1.2G)
NTFS (200G)
FreeBSD OS (250G)
NTFS (15G)
FAT-32 (100G) (needs to be RW for W7 and FreeBSD and ntfs-3g is just
not stable enough)
FreeBSD data only (380G)
The NTFS partitions are to place the Windows7 system, recovery
partition (which I may
not use), and Lenovo's odd SYSTEM_DRV that is required for booting.
gpart has no
indications of how to create an NTFS or FAT partition. Any way to so
this? Or, should I
use W7 to do that and leave the space for the FreeBSD ones?
No, you can do this with gpart.
gpart knows the following MS related GUIDs. The types you need
to use in -t are ms-basic-data, ms-ldm-data etc.
{ ms-basic-data, G_PART_ALIAS_MS_BASIC_DATA },
{ ms-ldm-data, G_PART_ALIAS_MS_LDM_DATA },
{ ms-ldm-metadata, G_PART_ALIAS_MS_LDM_METADATA },
{ ms-reserved, G_PART_ALIAS_MS_RESERVED },
{ ntfs, G_PART_ALIAS_MS_NTFS },
I don't know which partition types you should use for the
wanted partitioning scheme.
The struct that defines the known gpart GUIDs is in
/sys/geom/part/g_part.c at line 69(on HEAD).
HTH, Nikos
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Can gpart create ntfs and FAT-32 partitions?
I want to create a GPT disk structure that has the following partitions: MBR NTFS (1.2G) NTFS (200G) FreeBSD OS (250G) NTFS (15G) FAT-32 (100G) (needs to be RW for W7 and FreeBSD and ntfs-3g is just not stable enough) FreeBSD data only (380G) The NTFS partitions are to place the Windows7 system, recovery partition (which I may not use), and Lenovo's odd SYSTEM_DRV that is required for booting. gpart has no indications of how to create an NTFS or FAT partition. Any way to so this? Or, should I use W7 to do that and leave the space for the FreeBSD ones? -- R. Kevin Oberman, Network Engineer - Retired E-mail: kob6...@gmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Query about FreeBSD and primary partitions requirements
In freebsd-questions Digest, Vol 366, Issue 8, Message: 5
On Sat, 11 Jun 2011 14:23:48 -0700 per...@pluto.rain.com wrote:
Matthew Seaman m.sea...@infracaninophile.co.uk wrote:
On 11/06/2011 08:18, Bret Busby wrote:
the current FreeBSD Handbook ... states
FreeBSD must be installed into a primary partition.
However, in the last couple of days, I have been advised that
FreeBSD can be installed in, and, quite happily runs in, a
logical partition within an extended partition.
Has anyone other than the person who advised me of that, tested
the installation and operation of FreeBSD, within a logical
patition of an extended partition ...?
FreeBSD can mount and use filesystems created on partitions inside
'extended partition' type slices (cue standard exposition of the
difference between partitions and slices in FreeBSD-speak.) True.
However, I believe that you may well have difficulty *booting*
FreeBSD unless the kernel (ie. /boot) can be read from a primary
partition.
I presume the purpose of boot0ext.S is to build a boot0 (FreeBSD MBR)
variant capable of booting from what MS call an extended partition
-- boot0.S being used when booting from a primary partition -- but
I've never tried to use it. I'm having enough fun trying to boot
from a _different_ unusual configuration.
Diffing boot0.S and boot0ext.S shows the latter to be a two-sector (1KB)
boot with more detailed strings about different partition types, some
difference in SIO code, support for 'BIOS EDD extensions' and CHS vs LBA
(ie, older stuff) but nothing I could spot towards decoding 'extended
partitions'; it seems from CVS logs to have been kept as a nod to jhk's
original 2-sector boot0 code, and hasn't been touched for 7 years.
Having run OS/2 for several years before moving to FreeBSD in '98 I had
to learn about mounting 'drives' within 'extended partitions' as adXs5,
adXs6 etc, to recover about 7 OS/2 filesystems from 2 disks. Last I
looked the HPFS code was still in the tree, only needing compiling; very
similar to the (old) NTFS code by the same author, it worked fine R/O.
Anyway, space allocation within the 'extended partition' is implemented
as a linked list, so booting from one of these used to need something
like OS/2's boot manager (itself consuming a small primary partition) or
GRUB ono to chase down and load the desired boot partition, assuming you
managed from the command line to newfs it as UFS in the first place (?)
Also, I don't think sysinstall(8) groks extended partitions very
well,
if at all ...
Not at all; sysinstall just sees it as a primary partition (ie FreeBSD
slice) of type 0x05 (IIRC) ie as a non-bootable partition, completely
ignored by boot0{,ext} or any 'normal' MBR code for that matter .. the
FreeBSD convention of naming these as s5 etc is a convenient fiction.
so you will probably have some fun doing the actual installation.
Indeed.
Best left as an exercise for the (morbidly curious) student :)
cheers, Ian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Query about FreeBSD and primary partitions requirements
hello. Some time ago, I asked on this list, about installing FreeBSD, and it was then confirmed that FreeBSD requires to be installed in a primary partition. That is consistent with the current FreeBSD Handbook, which states FreeBSD must be installed into a primary partition. However, in the last couple of days, I have been advised that FreeBSD can be installed in, and, quite happily runs in, a logical partition within an extended partition. Has anyone other than the person who advised me of that, tested the installation and operation of FreeBSD, within a logical patition of an extended partition, that has given a result that confirms that FeeBSD can now be successfully installed and run, in a logical partition of an extended partition of a hard drive? Thank you in anticipation. -- Bret Busby Armadale West Australia .. So once you do know what the question actually is, you'll know what the answer means. - Deep Thought, Chapter 28 of Book 1 of The Hitchhiker's Guide to the Galaxy: A Trilogy In Four Parts, written by Douglas Adams, published by Pan Books, 1992 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Query about FreeBSD and primary partitions requirements
On 11/06/2011 08:18, Bret Busby wrote: Some time ago, I asked on this list, about installing FreeBSD, and it was then confirmed that FreeBSD requires to be installed in a primary partition. That is consistent with the current FreeBSD Handbook, which states FreeBSD must be installed into a primary partition. However, in the last couple of days, I have been advised that FreeBSD can be installed in, and, quite happily runs in, a logical partition within an extended partition. Has anyone other than the person who advised me of that, tested the installation and operation of FreeBSD, within a logical patition of an extended partition, that has given a result that confirms that FeeBSD can now be successfully installed and run, in a logical partition of an extended partition of a hard drive? FreeBSD can mount and use filesystems created on partitions inside 'extended partition' type slices (cue standard exposition of the difference between partitions and slices in FreeBSD-speak.) True. However, I believe that you may well have difficulty *booting* FreeBSD unless the kernel (ie. /boot) can be read from a primary partition. Also, I don't think sysinstall(8) groks extended partitions very well, so you will probably have some fun doing the actual installation. Certainly not impossible, but not something you should contemplate if you still consider yourself just a beginner. Of course, this discussion only applies to DOS MBR style partitioning, which is fairly rapidly going the way of the Dodo (at least in the FreeBSD world.) Unless you need the backwards compatibility, GPT looks like a much more attractive proposition for a new machine nowadays. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Query about FreeBSD and primary partitions requirements
Matthew Seaman m.sea...@infracaninophile.co.uk wrote: On 11/06/2011 08:18, Bret Busby wrote: the current FreeBSD Handbook ... states FreeBSD must be installed into a primary partition. However, in the last couple of days, I have been advised that FreeBSD can be installed in, and, quite happily runs in, a logical partition within an extended partition. Has anyone other than the person who advised me of that, tested the installation and operation of FreeBSD, within a logical patition of an extended partition ...? FreeBSD can mount and use filesystems created on partitions inside 'extended partition' type slices (cue standard exposition of the difference between partitions and slices in FreeBSD-speak.) True. However, I believe that you may well have difficulty *booting* FreeBSD unless the kernel (ie. /boot) can be read from a primary partition. I presume the purpose of boot0ext.S is to build a boot0 (FreeBSD MBR) variant capable of booting from what MS call an extended partition -- boot0.S being used when booting from a primary partition -- but I've never tried to use it. I'm having enough fun trying to boot from a _different_ unusual configuration. Also, I don't think sysinstall(8) groks extended partitions very well, if at all ... so you will probably have some fun doing the actual installation. Indeed. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: IDE -- mount partitions for better performance
On 14 March 2011 20:00, freebsd_u...@guice.ath.cx wrote: freebsd-questions@freebsd.org Guidance with the following: We are limited to Support for ATA-100/66/33 IDE and ATAPI compliant devices. With that said, we have our atapi/33 optical on a add in controller (PCI) and are seeking to place four HDD’s on the main boards controllers. Our dilemma is where to place /, /tmp, /usr and /var from a performance standpoint. We understand that /var does quite a bit of writing and probably should go on the master hdd, but what about the /usr, /tmp and root? Hell, I’m not sure my thinking is sane as to where I ‘think’ /var should be placed/mounted. It depends on very many things. tmpfs(5) has been extremely stable for me, definitely safe enough for /tmp. Make sure you have plenty of swap, though. If the bits in /var aren't life or death (or at least production mail-server) you can get by with it being mounted on a volatile filesystem (like tmpfs or mdmfs) and backed up occasionally (via cron or similar). If you absolutely can't afford to lose even 5 minutes of /var's past you'd be better off mirroring. I generally put / /usr on the same disk, they're reasonably small written to very little, if you symlink /usr/obj, /usr/src, /usr/ports. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: IDE -- mount partitions for better performance
Annotated below ... Hi, On Tuesday 15 March 2011 07:00:30 freebsd_u...@guice.ath.cx wrote: freebsd-questions@freebsd.org Guidance with the following: We are limited to Support for ATA-100/66/33 IDE and ATAPI compliant devices. With that said, we have our atapi/33 optical on a add in controller (PCI) and are seeking to place four HDDs on the main boards controllers. Our dilemma is where to place /, /tmp, /usr and /var from a performance standpoint. We understand that /var does quite a bit of writing and probably should go on the master hdd, but what about the /usr, /tmp and root? Hell, Im not sure my thinking is sane as to where I think /var should be placed/mounted. did I get it right? You have four hard disks? Yes, four separate HDD's If so, place /, /var /tmp on indiidual drives. Make the fourth disk usr and mount the remaining space of the other three disks inside /usr/home. Are you suggesting something similar to: /dev/ad4s1a for / /dev/ad4s2a for /tmp /dev/ad4s3a for /usr /dev/ad4s4a for /var If so, my initial can current concern is which device (hdd) from the above list/configuration, should be connected to which cable connector (master or slave)? --depending on how much writing to a particular device is taking place; for instance during a 'build world' or while building anything from src. there is quite a bit of writing going on. I would think that making the disk/slice that is being written to a slave would decrease performance when the master to that slave is also being written to simultaneously. In such a case the slave would need to wait until the master is done writing before the slave would be able to write; Is my thinking on this sane? Please enlighten me/us. Thank you. Locate then stuff on the other three disks which you expect to be used in parallel with the /usr disk. I'm lost on the above suggestion; not understanding this. Of course, you can mount it anywhere else if you want. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: IDE -- mount partitions for better performance
On Tue, Mar 15, 2011 at 3:17 PM, freebsd_u...@guice.ath.cx wrote: Annotated below ... Hi, On Tuesday 15 March 2011 07:00:30 freebsd_u...@guice.ath.cx wrote: freebsd-questions@freebsd.org Guidance with the following: We are limited to Support for ATA-100/66/33 IDE and ATAPI compliant devices. With that said, we have our atapi/33 optical on a add in controller (PCI) and are seeking to place four HDD’s on the main boards controllers. Our dilemma is where to place /, /tmp, /usr and /var from a performance standpoint. We understand that /var does quite a bit of writing and probably should go on the master hdd, but what about the /usr, /tmp and root? Hell, I’m not sure my thinking is sane as to where I ‘think’ /var should be placed/mounted. did I get it right? You have four hard disks? Yes, four separate HDD's If so, place /, /var /tmp on indiidual drives. Make the fourth disk usr and mount the remaining space of the other three disks inside /usr/home. Are you suggesting something similar to: /dev/ad4s1a for / /dev/ad4s2a for /tmp /dev/ad4s3a for /usr /dev/ad4s4a for /var If so, my initial can current concern is which device (hdd) from the above list/configuration, should be connected to which cable connector (master or slave)? --depending on how much writing to a particular device is taking place; for instance during a 'build world' or while building anything from src. there is quite a bit of writing going on. I would think that making the disk/slice that is being written to a slave would decrease performance when the master to that slave is also being written to simultaneously. In such a case the slave would need to wait until the master is done writing before the slave would be able to write; Is my thinking on this sane? Please enlighten me/us. Thank you. Locate then stuff on the other three disks which you expect to be used in parallel with the /usr disk. I'm lost on the above suggestion; not understanding this. Of course, you can mount it anywhere else if you want. Erich When four IDE hard disks are usable , then there should be at least two IDE connectors on the main board . IDE cables have two connectors ( connectors near to each other ) . The outer connector is for MASTER , the INNER connector is for SLAVE . IDE hard disks have JUMPERS to set the MASTER and SLAVE hard disks , and it is very likely that on the hard disk , information about jumper settings are printed . When there is no such information printed , it is possible that it is printed in its manual , or it may be available from its producer web site . MASTER hard disk should be connected to outer connector , SLAVE hard disk should be connected to INNER connector . Then , the computer will identify these hard disks with respect to connector on the main board , and MASTER and SLAVE settings of the hard disks . Then , it will list them as /dev/ad1... , /dev/ad2... , /dev/ad3... , /dev/ad4... , or other ad(Numbers) depending on mother board IDE ports settings ( there may be add-on IDE cards ) , or installer may label them differently . If the hard disks are different from each other , it is easy to identify which disk is detected as which device . ( Installer will list information about their sizes ( and , perhaps trade marks ) . ) Assume that all of the hard disks are the same . Then , it is very likely that the connector slot 0 will be detected first , and the connector slot 1 will be detected as second . To be exactly sure , the following steps may be applied . ( Absolutely power down the computer for hardware modifications ) : ( Record detected connected device names . ) ( On the mother board , slot numbers or letters may be printed explicitly . ) Disconnect connector in IDE slot 1 and detect disks in connector in IDE slot 0 . Then , disconnect connector in IDE slot 0 and connect IDE slot 1 connector and detect disks in IDE slot 1. Then , connect connector in IDE slot 0 and detect all of the disks . After obtaining exact device names of the hard disks , final installation may be performed . Thank you very much . Mehmet Erol Sanliturk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: IDE -- mount partitions for better performance
On Tue, 15 Mar 2011 15:17:34 -0400, freebsd_u...@guice.ath.cx wrote: did I get it right? You have four hard disks? Yes, four separate HDD's I assume you have two on each of the two lines: ad0 = primary master ad1 = primary slave ad2 = secondary master ad3 = secondary slave This is how they would be connected: =primary=ad0-ad1 =secondary===ad2-ad3 Are you suggesting something similar to: /dev/ad4s1a for / /dev/ad4s2a for /tmp /dev/ad4s3a for /usr /dev/ad4s4a for /var No. You don't need to even slice the disks (if you're running FreeBSD only, use dangerously dedicated layout). But if you require compatibility, make the following layout (just a suggestion): ad0s1a = / ad0s1d = /usr ad1s1a = /tmp ad1s1b = swap ad2s1a = /var ad3s1a = /home Keep in mind that performance across ad0 and ad2 is best. Masters are always good. Slaves are slower. Using primary and secondary in parallel works good, working on a master and a slave simultanously is worse. So you have the chance to put different subtrees (for example /usr/obj or /usr/src) on different partitions, drives and lines if needed. The positioning always depends on how much activity you expect on the certain file systems. You did get this idea already. Example: /usr is on prim. master, 2nd partition /usr/obj is mounted to /var/uobj on sec. master, 2nd partition You could also add - with the known limitations (fixed size) - other partitions depending on R/W activity, for example if you need /export or /opt. I have successfully used similar approaches in the past, also using (P)ATA disks, but I had them on a separate controller (also 2 ATA channels, just as you use them from the mainboard). If you omit the slicing step, all examples remove s1. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: IDE -- mount partitions for better performance
On Tue, Mar 15, 2011 at 3:59 PM, Polytropon free...@edvax.de wrote: Keep in mind that performance across ad0 and ad2 is best. Masters are always good. Slaves are slower. Using primary and secondary in parallel works good, working on a master and a slave simultanously is worse. Your statement about master being faster than a slave is simply not true for almost every scenario when using devices with same capabilites. All master/slave really controls is enumeration, and shouldn't effect performance in and of itself. Other variables can effect that of course, like using a slower device as an ATA Device-1 with a faster Device-0. Even that example isn't ubiquitous as many, maybe most controllers are able to support mixed devices each in their fastest mode. The whole IDE device contention really isn't much of a bottle neck in this scenario. It's only a big factor when there's *a lot* of simultaneous IO going to both, say dumping one disk to another. The highest preforming setup in something like this is likely to be something along the lines of a 4-way /boot gmirror, and a 4-way gstripe with a smaller stripe size eg 32k across the remaining usable space. If you aggregate your disk IO in this manner, IDE channel contention shouldn't be much of a bottleneck. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: IDE -- mount partitions for better performance
On Tue, 15 Mar 2011 17:07:20 -0500, Adam Vande More amvandem...@gmail.com wrote: Your statement about master being faster than a slave is simply not true for almost every scenario when using devices with same capabilites. All master/slave really controls is enumeration, and shouldn't effect performance in and of itself. Other variables can effect that of course, like using a slower device as an ATA Device-1 with a faster Device-0. Even that example isn't ubiquitous as many, maybe most controllers are able to support mixed devices each in their fastest mode. My statement originates back from individual experience in settings where disks with different capabilities (esp. very old + very new disk), as well as disk drive and an optical drive with limited speed. The whole IDE device contention really isn't much of a bottle neck in this scenario. It's only a big factor when there's *a lot* of simultaneous IO going to both, say dumping one disk to another. That's true: When copying (or moving) data from one disk to the other master-master seems to be faster than master-slave (same line), if I remember correctly. The highest preforming setup in something like this is likely to be something along the lines of a 4-way /boot gmirror, and a 4-way gstripe with a smaller stripe size eg 32k across the remaining usable space. If you aggregate your disk IO in this manner, IDE channel contention shouldn't be much of a bottleneck. A good advice, I haven't thought of that (never tried, but sounds achievable). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
IDE -- mount partitions for better performance
freebsd-questions@freebsd.org Guidance with the following: We are limited to Support for ATA-100/66/33 IDE and ATAPI compliant devices. With that said, we have our atapi/33 optical on a add in controller (PCI) and are seeking to place four HDDs on the main boards controllers. Our dilemma is where to place /, /tmp, /usr and /var from a performance standpoint. We understand that /var does quite a bit of writing and probably should go on the master hdd, but what about the /usr, /tmp and root? Hell, Im not sure my thinking is sane as to where I think /var should be placed/mounted. Thanks for the read of this. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: IDE -- mount partitions for better performance
Hi, On Tuesday 15 March 2011 07:00:30 freebsd_u...@guice.ath.cx wrote: freebsd-questions@freebsd.org Guidance with the following: We are limited to Support for ATA-100/66/33 IDE and ATAPI compliant devices. With that said, we have our atapi/33 optical on a add in controller (PCI) and are seeking to place four HDDs on the main boards controllers. Our dilemma is where to place /, /tmp, /usr and /var from a performance standpoint. We understand that /var does quite a bit of writing and probably should go on the master hdd, but what about the /usr, /tmp and root? Hell, Im not sure my thinking is sane as to where I think /var should be placed/mounted. did I get it right? You have four hard disks? If so, place /, /var /tmp on indiidual drives. Make the fourth disk usr and mount the remaining space of the other three disks inside /usr/home. Locate then stuff on the other three disks which you expect to be used in parallel with the /usr disk. Of course, you can mount it anywhere else if you want. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ROOT on ZFS with MBR partitions
On Sun, Feb 27, 2011 at 12:45 AM, Daniel Staal dst...@usa.net wrote: --As of February 27, 2011 12:26:04 AM +, Slawomir Wojtczak is alleged to have said: ... but none of them seems to work, after installation it hangs at boot like that: http://ompldr.org/vN2tscQ --As for the rest, it is mine. Hmm. Interesting. I'm having the same result when trying the 'root on ZFS, boot from UFS' guide here: http://wiki.freebsd.org/RootOnZFS/UFSBoot Anything interesting happening during your install? I have an error late in the process (During 'Step 3.1') with this command: Fixit# mv boot bootdir/ It gives me an error saying that /bin/cp can't found/executed. (I've been trying to work around using `bin/cp -pRP boot bootdir/`. Note the lack of the leading slash.) I had tried several of the other installs from http://wiki.freebsd.org/RootOnZFS successfully, but I don't think I'd tried the MBR install. Daniel T. Staal I had the same problem. Today, I tried using the PCBSD dvd to install FreeBSD on ZFS (with /boot on UFS). It kept giving errors just before completion. However, some comments I found while googling about that problem mentioned that the installation seemed to have completed, which seems to be the case. Both FreeBSD and FreeDOS are now installed on the same drive (in a VM, I'll try this on real h/w next). Still not sure what caused the error during installation though. Regards Gautham Ganapathy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ROOT on ZFS with MBR partitions
Hi, I have tried these guides: http://wiki.freebsd.org/RootOnZFS/ZFSBootSlice http://wiki.freebsd.org/RootOnZFS/ZFSBootPartition ... but none of them seems to work, after installation it hangs at boot like that: http://ompldr.org/vN2tscQ I am using these guides with 8.2-RELEASE amd64 version. I know that there is way to do this on GPT partitions, but I need MBR ones ... Any help appreciated, vermaden ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ROOT on ZFS with MBR partitions
--As of February 27, 2011 12:26:04 AM +, Slawomir Wojtczak is alleged to have said: ... but none of them seems to work, after installation it hangs at boot like that: http://ompldr.org/vN2tscQ --As for the rest, it is mine. Hmm. Interesting. I'm having the same result when trying the 'root on ZFS, boot from UFS' guide here: http://wiki.freebsd.org/RootOnZFS/UFSBoot Anything interesting happening during your install? I have an error late in the process (During 'Step 3.1') with this command: Fixit# mv boot bootdir/ It gives me an error saying that /bin/cp can't found/executed. (I've been trying to work around using `bin/cp -pRP boot bootdir/`. Note the lack of the leading slash.) I had tried several of the other installs from http://wiki.freebsd.org/RootOnZFS successfully, but I don't think I'd tried the MBR install. Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ROOT on ZFS with MBR partitions
Anything interesting happening during your install? I would say no, everything seems smooth until I try to boot it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ROOT on ZFS with MBR partitions
How long are you waiting? What are you booting from? On Sat, Feb 26, 2011 at 7:54 PM, Slawomir Wojtczak verma...@gmx.com wrote: Anything interesting happening during your install? I would say no, everything seems smooth until I try to boot it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Partitions greater than 1TB ?
It does the trick, thank you this could help http://romain.blogreen.org/Blog/Updating_FreeBSD_7_%28i386%29_to_8_%28amd64%29 On 01/25/2011 12:51 AM, Devin Teske wrote: On Mon, 2011-01-24 at 15:08 +0100, Frank Bonnet wrote: Hello I'm trying to install a new server ( HP Proliant 380 G7 ) which has a 2.5 TB RAID Array. It seems impossible to use the Freebsd sysinstall to partition this raid array disks. Correct. Currently sysinstall can only perform MBR partitioning (partitions limited to 2TB max). You want GPT partitioning. See gpart(8) -- Devin I get an error message when running the partitionner Error mounting /mnt/dev/da1s1e on /mnt/.user : input/output error Anyone has infos about this problem ? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. _ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Frank BONNET 01.45.92.66.17 Service des Moyens Informatique Generaux ESIEE PARIS Cité Descartes / BP 99 93162 NOISY-LE-GRAND Cedex http://www.esiee.fr http://www.esiee.fr/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Partitions greater than 1TB ?
Hello I'm trying to install a new server ( HP Proliant 380 G7 ) which has a 2.5 TB RAID Array. It seems impossible to use the Freebsd sysinstall to partition this raid array disks. I get an error message when running the partitionner Error mounting /mnt/dev/da1s1e on /mnt/.user : input/output error Anyone has infos about this problem ? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Partitions greater than 1TB ?
On Mon, 2011-01-24 at 15:08 +0100, Frank Bonnet wrote: Hello I'm trying to install a new server ( HP Proliant 380 G7 ) which has a 2.5 TB RAID Array. It seems impossible to use the Freebsd sysinstall to partition this raid array disks. Correct. Currently sysinstall can only perform MBR partitioning (partitions limited to 2TB max). You want GPT partitioning. See gpart(8) -- Devin I get an error message when running the partitionner Error mounting /mnt/dev/da1s1e on /mnt/.user : input/output error Anyone has infos about this problem ? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. _ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8 partitions maximum
On 12/01/10 21:23, David DEMELIER wrote: Yes it is just exercises, I heard bsdlabel was grow up so I wanted to test, now I don't really understand why it's fixed to 20 only. I also It turns out that something like 22.75 bsdlabel partition table entries fit in a 512 byte sector, so this was rounded down to 20. This is where this limit comes from - the size of the sector. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8 partitions maximum
On 12/1/10, David Demelier demelier.da...@gmail.com wrote: On 30/11/2010 23:29, Paul B Mahol wrote: On 11/30/10, David DEMELIERdemelier.da...@gmail.com wrote: 2010/11/30 Paul B Maholone...@gmail.com: On 11/30/10, David DEMELIERdemelier.da...@gmail.com wrote: 2010/11/30 Patrick Lamaizierepatf...@davenulle.org: Le Tue, 30 Nov 2010 21:45:03 +0100, David Demelierdemelier.da...@gmail.com a ecrit : Hello, Hello, We all know that we can only have 8 ufs partitions in one freebsd slice. Since OpenBSD and NetBSD can support at most 32 partitions iirc. I wonder why FreeBSD still lacks more ufs partitions in one slice? Is there any plan to grow up max partitions or every work is dedicated to ZFS? hmmm, isn't already done in 8.X ? from what's cooking for FreeBSD 8.0 http://ivoras.sharanet.org/freebsd/freebsd8.html bsdlabel gets extended to 26 partitions Status: Committed to -CURRENT Will appear in 8.0: sure Author: Marcel Moolenaar Web: commit message bsdlabel is (finally!) extended to support more than 8 partitions. The new limit of 26 partitions comes from the number of lower-case letters. To make use of this change, GEOM_PART needs to be used instead of GEOM_BSD (this is default in 8.0 but will not work with older kernels). I don't have GEOM_PART in my kernel, but if you said it's default it should be pulled in. Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org But why : # /dev/md2s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 10m 164.2BSD0 0 b: 10m *4.2BSD0 0 d: 10m *4.2BSD0 0 e: 10m *4.2BSD0 0 f: 10m *4.2BSD0 0 g: 10m *4.2BSD0 0 h: 10m *4.2BSD0 0 i: 10m *4.2BSD0 0 j: 10m *4.2BSD0 0 k: 10m *4.2BSD0 0 c: 20479730unused0 0 # raw part, don't edit line 11: partition name out of range a-h: i line 12: partition name out of range a-h: j line 13: partition name out of range a-h: k re-edit the label? [y]: I'm on 8.1-RELEASE. To make use of such feature you need to recreate table with gpart(8). bsdlabel is not going to work. mark...@melon ~ $ sudo dd if=/dev/zero of=myfile.img bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 2.095537 secs (50038530 bytes/sec) mark...@melon ~ $ sudo mdconfig -a -f myfile.img -u 2 mark...@melon ~ $ sudo gpart create -s MBR md2 md2 created mark...@melon ~ $ sudo gpart show md2s1 gpart: No such geom: md2s1. mark...@melon ~ $ sudo gpart add -t freebsd md2 md2s1 added mark...@melon ~ $ sudo gpart add -t freebsd-ufs md2s1 gpart: No such geom: md2s1. mark...@melon ~ $ sudo gpart create -s BSD md2s1 gpart create -s BSD -n 26 md2s1 mark...@melon ~ $ sudo gpart create -s BSD -n 26 md0s1 gpart: entries '26': Invalid argument mark...@melon ~ $ sudo gpart create -s BSD -n 8 md0s1 md0s1 created Looks like max number is 20, up to md2s1t. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8 partitions maximum
2010/12/1 Paul B Mahol one...@gmail.com: On 12/1/10, David Demelier demelier.da...@gmail.com wrote: On 30/11/2010 23:29, Paul B Mahol wrote: On 11/30/10, David DEMELIERdemelier.da...@gmail.com wrote: 2010/11/30 Paul B Maholone...@gmail.com: On 11/30/10, David DEMELIERdemelier.da...@gmail.com wrote: 2010/11/30 Patrick Lamaizierepatf...@davenulle.org: Le Tue, 30 Nov 2010 21:45:03 +0100, David Demelierdemelier.da...@gmail.com a ecrit : Hello, Hello, We all know that we can only have 8 ufs partitions in one freebsd slice. Since OpenBSD and NetBSD can support at most 32 partitions iirc. I wonder why FreeBSD still lacks more ufs partitions in one slice? Is there any plan to grow up max partitions or every work is dedicated to ZFS? hmmm, isn't already done in 8.X ? from what's cooking for FreeBSD 8.0 http://ivoras.sharanet.org/freebsd/freebsd8.html bsdlabel gets extended to 26 partitions Status: Committed to -CURRENT Will appear in 8.0: sure Author: Marcel Moolenaar Web: commit message bsdlabel is (finally!) extended to support more than 8 partitions. The new limit of 26 partitions comes from the number of lower-case letters. To make use of this change, GEOM_PART needs to be used instead of GEOM_BSD (this is default in 8.0 but will not work with older kernels). I don't have GEOM_PART in my kernel, but if you said it's default it should be pulled in. Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org But why : # /dev/md2s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 10m 16 4.2BSD 0 0 b: 10m * 4.2BSD 0 0 d: 10m * 4.2BSD 0 0 e: 10m * 4.2BSD 0 0 f: 10m * 4.2BSD 0 0 g: 10m * 4.2BSD 0 0 h: 10m * 4.2BSD 0 0 i: 10m * 4.2BSD 0 0 j: 10m * 4.2BSD 0 0 k: 10m * 4.2BSD 0 0 c: 2047973 0 unused 0 0 # raw part, don't edit line 11: partition name out of range a-h: i line 12: partition name out of range a-h: j line 13: partition name out of range a-h: k re-edit the label? [y]: I'm on 8.1-RELEASE. To make use of such feature you need to recreate table with gpart(8). bsdlabel is not going to work. mark...@melon ~ $ sudo dd if=/dev/zero of=myfile.img bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 2.095537 secs (50038530 bytes/sec) mark...@melon ~ $ sudo mdconfig -a -f myfile.img -u 2 mark...@melon ~ $ sudo gpart create -s MBR md2 md2 created mark...@melon ~ $ sudo gpart show md2s1 gpart: No such geom: md2s1. mark...@melon ~ $ sudo gpart add -t freebsd md2 md2s1 added mark...@melon ~ $ sudo gpart add -t freebsd-ufs md2s1 gpart: No such geom: md2s1. mark...@melon ~ $ sudo gpart create -s BSD md2s1 gpart create -s BSD -n 26 md2s1 mark...@melon ~ $ sudo gpart create -s BSD -n 26 md0s1 gpart: entries '26': Invalid argument mark...@melon ~ $ sudo gpart create -s BSD -n 8 md0s1 md0s1 created Looks like max number is 20, up to md2s1t. Yes I saw that it was only 20 max, so how to get 26 partitions using bsdlabel ? :-) Cheers, -- Demelier David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8 partitions maximum
On 12/1/10, David DEMELIER demelier.da...@gmail.com wrote: 2010/12/1 Paul B Mahol one...@gmail.com: On 12/1/10, David Demelier demelier.da...@gmail.com wrote: On 30/11/2010 23:29, Paul B Mahol wrote: On 11/30/10, David DEMELIERdemelier.da...@gmail.com wrote: 2010/11/30 Paul B Maholone...@gmail.com: On 11/30/10, David DEMELIERdemelier.da...@gmail.com wrote: 2010/11/30 Patrick Lamaizierepatf...@davenulle.org: Le Tue, 30 Nov 2010 21:45:03 +0100, David Demelierdemelier.da...@gmail.com a ecrit : Hello, Hello, We all know that we can only have 8 ufs partitions in one freebsd slice. Since OpenBSD and NetBSD can support at most 32 partitions iirc. I wonder why FreeBSD still lacks more ufs partitions in one slice? Is there any plan to grow up max partitions or every work is dedicated to ZFS? hmmm, isn't already done in 8.X ? from what's cooking for FreeBSD 8.0 http://ivoras.sharanet.org/freebsd/freebsd8.html bsdlabel gets extended to 26 partitions Status: Committed to -CURRENT Will appear in 8.0: sure Author: Marcel Moolenaar Web: commit message bsdlabel is (finally!) extended to support more than 8 partitions. The new limit of 26 partitions comes from the number of lower-case letters. To make use of this change, GEOM_PART needs to be used instead of GEOM_BSD (this is default in 8.0 but will not work with older kernels). I don't have GEOM_PART in my kernel, but if you said it's default it should be pulled in. Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org But why : # /dev/md2s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 10m 164.2BSD0 0 b: 10m *4.2BSD0 0 d: 10m *4.2BSD0 0 e: 10m *4.2BSD0 0 f: 10m *4.2BSD0 0 g: 10m *4.2BSD0 0 h: 10m *4.2BSD0 0 i: 10m *4.2BSD0 0 j: 10m *4.2BSD0 0 k: 10m *4.2BSD0 0 c: 20479730unused0 0 # raw part, don't edit line 11: partition name out of range a-h: i line 12: partition name out of range a-h: j line 13: partition name out of range a-h: k re-edit the label? [y]: I'm on 8.1-RELEASE. To make use of such feature you need to recreate table with gpart(8). bsdlabel is not going to work. mark...@melon ~ $ sudo dd if=/dev/zero of=myfile.img bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 2.095537 secs (50038530 bytes/sec) mark...@melon ~ $ sudo mdconfig -a -f myfile.img -u 2 mark...@melon ~ $ sudo gpart create -s MBR md2 md2 created mark...@melon ~ $ sudo gpart show md2s1 gpart: No such geom: md2s1. mark...@melon ~ $ sudo gpart add -t freebsd md2 md2s1 added mark...@melon ~ $ sudo gpart add -t freebsd-ufs md2s1 gpart: No such geom: md2s1. mark...@melon ~ $ sudo gpart create -s BSD md2s1 gpart create -s BSD -n 26 md2s1 mark...@melon ~ $ sudo gpart create -s BSD -n 26 md0s1 gpart: entries '26': Invalid argument mark...@melon ~ $ sudo gpart create -s BSD -n 8 md0s1 md0s1 created Looks like max number is 20, up to md2s1t. Yes I saw that it was only 20 max, so how to get 26 partitions using bsdlabel ? :-) It is hardcoded. Not my code. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8 partitions maximum
On Wed, 1 Dec 2010 13:51:48 + Paul B Mahol one...@gmail.com wrote: [snip 9 levels of quoting] It is hardcoded. Not my code. Could you remember to remove excess quotes please? It's getting a bit ridiculous having to scroll past 50 lines to see a one-line reply :) -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8 partitions maximum
On 1 December 2010 14:13, Bruce Cran br...@cran.org.uk wrote: On Wed, 1 Dec 2010 13:51:48 + Paul B Mahol one...@gmail.com wrote: [snip 9 levels of quoting] It is hardcoded. Not my code. Could you remember to remove excess quotes please? It's getting a bit ridiculous having to scroll past 50 lines to see a one-line reply :) -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Is this a theoretical exercise as I cant see why you would need that many file systems? Why not just use a EFI layout then you can have 128 file sytems? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8 partitions maximum
2010/12/1 krad kra...@gmail.com: On 1 December 2010 14:13, Bruce Cran br...@cran.org.uk wrote: On Wed, 1 Dec 2010 13:51:48 + Paul B Mahol one...@gmail.com wrote: [snip 9 levels of quoting] It is hardcoded. Not my code. Could you remember to remove excess quotes please? It's getting a bit ridiculous having to scroll past 50 lines to see a one-line reply :) -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Is this a theoretical exercise as I cant see why you would need that many file systems? Why not just use a EFI layout then you can have 128 file sytems? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Yes it is just exercises, I heard bsdlabel was grow up so I wanted to test, now I don't really understand why it's fixed to 20 only. I also wanted to try partitionning a disk using only gpart and not fdisk/bsdlabel at all so to check if what announced is real but it seems not :-). Kind regards, -- Demelier David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
8 partitions maximum
Hello, We all know that we can only have 8 ufs partitions in one freebsd slice. Since OpenBSD and NetBSD can support at most 32 partitions iirc. I wonder why FreeBSD still lacks more ufs partitions in one slice? Is there any plan to grow up max partitions or every work is dedicated to ZFS? Kind regards, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8 partitions maximum
On Tue, 30 Nov 2010 21:45:03 +0100, David Demelier demelier.da...@gmail.com wrote: Since OpenBSD and NetBSD can support at most 32 partitions iirc. I thought the limit was 26, as the letters a to z... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8 partitions maximum
On 11/30/10, David Demelier demelier.da...@gmail.com wrote: Hello, We all know that we can only have 8 ufs partitions in one freebsd slice. Since OpenBSD and NetBSD can support at most 32 partitions iirc. I wonder why FreeBSD still lacks more ufs partitions in one slice? Actually FreeBSD supports more that 8 ufs partitions via gpart(8). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8 partitions maximum
Le Tue, 30 Nov 2010 21:45:03 +0100, David Demelier demelier.da...@gmail.com a écrit : Hello, Hello, We all know that we can only have 8 ufs partitions in one freebsd slice. Since OpenBSD and NetBSD can support at most 32 partitions iirc. I wonder why FreeBSD still lacks more ufs partitions in one slice? Is there any plan to grow up max partitions or every work is dedicated to ZFS? hmmm, isn't already done in 8.X ? from what's cooking for FreeBSD 8.0 http://ivoras.sharanet.org/freebsd/freebsd8.html « bsdlabel gets extended to 26 partitions Status: Committed to -CURRENT Will appear in 8.0: sure Author: Marcel Moolenaar Web: commit message bsdlabel is (finally!) extended to support more than 8 partitions. The new limit of 26 partitions comes from the number of lower-case letters. To make use of this change, GEOM_PART needs to be used instead of GEOM_BSD (this is default in 8.0 but will not work with older kernels). » Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8 partitions maximum
2010/11/30 Patrick Lamaiziere patf...@davenulle.org: Le Tue, 30 Nov 2010 21:45:03 +0100, David Demelier demelier.da...@gmail.com a écrit : Hello, Hello, We all know that we can only have 8 ufs partitions in one freebsd slice. Since OpenBSD and NetBSD can support at most 32 partitions iirc. I wonder why FreeBSD still lacks more ufs partitions in one slice? Is there any plan to grow up max partitions or every work is dedicated to ZFS? hmmm, isn't already done in 8.X ? from what's cooking for FreeBSD 8.0 http://ivoras.sharanet.org/freebsd/freebsd8.html « bsdlabel gets extended to 26 partitions Status: Committed to -CURRENT Will appear in 8.0: sure Author: Marcel Moolenaar Web: commit message bsdlabel is (finally!) extended to support more than 8 partitions. The new limit of 26 partitions comes from the number of lower-case letters. To make use of this change, GEOM_PART needs to be used instead of GEOM_BSD (this is default in 8.0 but will not work with older kernels). » I don't have GEOM_PART in my kernel, but if you said it's default it should be pulled in. Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org But why : # /dev/md2s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 10m 164.2BSD0 0 b: 10m *4.2BSD0 0 d: 10m *4.2BSD0 0 e: 10m *4.2BSD0 0 f: 10m *4.2BSD0 0 g: 10m *4.2BSD0 0 h: 10m *4.2BSD0 0 i: 10m *4.2BSD0 0 j: 10m *4.2BSD0 0 k: 10m *4.2BSD0 0 c: 20479730unused0 0 # raw part, don't edit line 11: partition name out of range a-h: i line 12: partition name out of range a-h: j line 13: partition name out of range a-h: k re-edit the label? [y]: I'm on 8.1-RELEASE. Cheers, -- Demelier David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8 partitions maximum
On 11/30/10, David DEMELIER demelier.da...@gmail.com wrote: 2010/11/30 Patrick Lamaiziere patf...@davenulle.org: Le Tue, 30 Nov 2010 21:45:03 +0100, David Demelier demelier.da...@gmail.com a ecrit : Hello, Hello, We all know that we can only have 8 ufs partitions in one freebsd slice. Since OpenBSD and NetBSD can support at most 32 partitions iirc. I wonder why FreeBSD still lacks more ufs partitions in one slice? Is there any plan to grow up max partitions or every work is dedicated to ZFS? hmmm, isn't already done in 8.X ? from what's cooking for FreeBSD 8.0 http://ivoras.sharanet.org/freebsd/freebsd8.html bsdlabel gets extended to 26 partitions Status: Committed to -CURRENT Will appear in 8.0: sure Author: Marcel Moolenaar Web: commit message bsdlabel is (finally!) extended to support more than 8 partitions. The new limit of 26 partitions comes from the number of lower-case letters. To make use of this change, GEOM_PART needs to be used instead of GEOM_BSD (this is default in 8.0 but will not work with older kernels). I don't have GEOM_PART in my kernel, but if you said it's default it should be pulled in. Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org But why : # /dev/md2s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 10m 164.2BSD0 0 b: 10m *4.2BSD0 0 d: 10m *4.2BSD0 0 e: 10m *4.2BSD0 0 f: 10m *4.2BSD0 0 g: 10m *4.2BSD0 0 h: 10m *4.2BSD0 0 i: 10m *4.2BSD0 0 j: 10m *4.2BSD0 0 k: 10m *4.2BSD0 0 c: 20479730unused0 0 # raw part, don't edit line 11: partition name out of range a-h: i line 12: partition name out of range a-h: j line 13: partition name out of range a-h: k re-edit the label? [y]: I'm on 8.1-RELEASE. To make use of such feature you need to recreate table with gpart(8). bsdlabel is not going to work. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8 partitions maximum
2010/11/30 Paul B Mahol one...@gmail.com: On 11/30/10, David DEMELIER demelier.da...@gmail.com wrote: 2010/11/30 Patrick Lamaiziere patf...@davenulle.org: Le Tue, 30 Nov 2010 21:45:03 +0100, David Demelier demelier.da...@gmail.com a ecrit : Hello, Hello, We all know that we can only have 8 ufs partitions in one freebsd slice. Since OpenBSD and NetBSD can support at most 32 partitions iirc. I wonder why FreeBSD still lacks more ufs partitions in one slice? Is there any plan to grow up max partitions or every work is dedicated to ZFS? hmmm, isn't already done in 8.X ? from what's cooking for FreeBSD 8.0 http://ivoras.sharanet.org/freebsd/freebsd8.html bsdlabel gets extended to 26 partitions Status: Committed to -CURRENT Will appear in 8.0: sure Author: Marcel Moolenaar Web: commit message bsdlabel is (finally!) extended to support more than 8 partitions. The new limit of 26 partitions comes from the number of lower-case letters. To make use of this change, GEOM_PART needs to be used instead of GEOM_BSD (this is default in 8.0 but will not work with older kernels). I don't have GEOM_PART in my kernel, but if you said it's default it should be pulled in. Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org But why : # /dev/md2s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 10m 16 4.2BSD 0 0 b: 10m * 4.2BSD 0 0 d: 10m * 4.2BSD 0 0 e: 10m * 4.2BSD 0 0 f: 10m * 4.2BSD 0 0 g: 10m * 4.2BSD 0 0 h: 10m * 4.2BSD 0 0 i: 10m * 4.2BSD 0 0 j: 10m * 4.2BSD 0 0 k: 10m * 4.2BSD 0 0 c: 2047973 0 unused 0 0 # raw part, don't edit line 11: partition name out of range a-h: i line 12: partition name out of range a-h: j line 13: partition name out of range a-h: k re-edit the label? [y]: I'm on 8.1-RELEASE. To make use of such feature you need to recreate table with gpart(8). bsdlabel is not going to work. mark...@melon ~ $ sudo dd if=/dev/zero of=myfile.img bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 2.095537 secs (50038530 bytes/sec) mark...@melon ~ $ sudo mdconfig -a -f myfile.img -u 2 mark...@melon ~ $ sudo gpart create -s MBR md2 md2 created mark...@melon ~ $ sudo gpart show md2s1 gpart: No such geom: md2s1. mark...@melon ~ $ sudo gpart add -t freebsd md2 md2s1 added mark...@melon ~ $ sudo gpart add -t freebsd-ufs md2s1 gpart: No such geom: md2s1. mark...@melon ~ $ sudo gpart create -s BSD md2s1 md2s1 created mark...@melon ~ $ sudo gpart add -t freebsd-ufs -s 1m md2s1 md2s1a added mark...@melon ~ $ sudo gpart add -t freebsd-ufs -s 1m md2s1 md2s1b added mark...@melon ~ $ sudo gpart add -t freebsd-ufs -s 1m md2s1 md2s1d added mark...@melon ~ $ sudo gpart add -t freebsd-ufs -s 1m md2s1 md2s1e added mark...@melon ~ $ sudo gpart add -t freebsd-ufs -s 1m md2s1 md2s1f added mark...@melon ~ $ sudo gpart add -t freebsd-ufs -s 1m md2s1 md2s1g added mark...@melon ~ $ sudo gpart add -t freebsd-ufs -s 1m md2s1 md2s1h added mark...@melon ~ $ sudo gpart add -t freebsd-ufs -s 1m md2s1 gpart: index '9': No space left on device mark...@melon ~ $ sudo gpart add -t freebsd-ufs -s 1m md2s1 gpart: index '9': No space left on device Maybe I really need GEOM_PART? Or I'm doing something wrong. -- Demelier David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8 partitions maximum
On 11/30/10, David DEMELIER demelier.da...@gmail.com wrote: 2010/11/30 Paul B Mahol one...@gmail.com: On 11/30/10, David DEMELIER demelier.da...@gmail.com wrote: 2010/11/30 Patrick Lamaiziere patf...@davenulle.org: Le Tue, 30 Nov 2010 21:45:03 +0100, David Demelier demelier.da...@gmail.com a ecrit : Hello, Hello, We all know that we can only have 8 ufs partitions in one freebsd slice. Since OpenBSD and NetBSD can support at most 32 partitions iirc. I wonder why FreeBSD still lacks more ufs partitions in one slice? Is there any plan to grow up max partitions or every work is dedicated to ZFS? hmmm, isn't already done in 8.X ? from what's cooking for FreeBSD 8.0 http://ivoras.sharanet.org/freebsd/freebsd8.html bsdlabel gets extended to 26 partitions Status: Committed to -CURRENT Will appear in 8.0: sure Author: Marcel Moolenaar Web: commit message bsdlabel is (finally!) extended to support more than 8 partitions. The new limit of 26 partitions comes from the number of lower-case letters. To make use of this change, GEOM_PART needs to be used instead of GEOM_BSD (this is default in 8.0 but will not work with older kernels). I don't have GEOM_PART in my kernel, but if you said it's default it should be pulled in. Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org But why : # /dev/md2s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 10m 164.2BSD0 0 b: 10m *4.2BSD0 0 d: 10m *4.2BSD0 0 e: 10m *4.2BSD0 0 f: 10m *4.2BSD0 0 g: 10m *4.2BSD0 0 h: 10m *4.2BSD0 0 i: 10m *4.2BSD0 0 j: 10m *4.2BSD0 0 k: 10m *4.2BSD0 0 c: 20479730unused0 0 # raw part, don't edit line 11: partition name out of range a-h: i line 12: partition name out of range a-h: j line 13: partition name out of range a-h: k re-edit the label? [y]: I'm on 8.1-RELEASE. To make use of such feature you need to recreate table with gpart(8). bsdlabel is not going to work. mark...@melon ~ $ sudo dd if=/dev/zero of=myfile.img bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 2.095537 secs (50038530 bytes/sec) mark...@melon ~ $ sudo mdconfig -a -f myfile.img -u 2 mark...@melon ~ $ sudo gpart create -s MBR md2 md2 created mark...@melon ~ $ sudo gpart show md2s1 gpart: No such geom: md2s1. mark...@melon ~ $ sudo gpart add -t freebsd md2 md2s1 added mark...@melon ~ $ sudo gpart add -t freebsd-ufs md2s1 gpart: No such geom: md2s1. mark...@melon ~ $ sudo gpart create -s BSD md2s1 gpart create -s BSD -n 26 md2s1 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8 partitions maximum
2010/11/30 Paul B Mahol one...@gmail.com: On 11/30/10, David DEMELIER demelier.da...@gmail.com wrote: 2010/11/30 Paul B Mahol one...@gmail.com: On 11/30/10, David DEMELIER demelier.da...@gmail.com wrote: 2010/11/30 Patrick Lamaiziere patf...@davenulle.org: Le Tue, 30 Nov 2010 21:45:03 +0100, David Demelier demelier.da...@gmail.com a ecrit : Hello, Hello, We all know that we can only have 8 ufs partitions in one freebsd slice. Since OpenBSD and NetBSD can support at most 32 partitions iirc. I wonder why FreeBSD still lacks more ufs partitions in one slice? Is there any plan to grow up max partitions or every work is dedicated to ZFS? hmmm, isn't already done in 8.X ? from what's cooking for FreeBSD 8.0 http://ivoras.sharanet.org/freebsd/freebsd8.html bsdlabel gets extended to 26 partitions Status: Committed to -CURRENT Will appear in 8.0: sure Author: Marcel Moolenaar Web: commit message bsdlabel is (finally!) extended to support more than 8 partitions. The new limit of 26 partitions comes from the number of lower-case letters. To make use of this change, GEOM_PART needs to be used instead of GEOM_BSD (this is default in 8.0 but will not work with older kernels). I don't have GEOM_PART in my kernel, but if you said it's default it should be pulled in. Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org But why : # /dev/md2s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 10m 16 4.2BSD 0 0 b: 10m * 4.2BSD 0 0 d: 10m * 4.2BSD 0 0 e: 10m * 4.2BSD 0 0 f: 10m * 4.2BSD 0 0 g: 10m * 4.2BSD 0 0 h: 10m * 4.2BSD 0 0 i: 10m * 4.2BSD 0 0 j: 10m * 4.2BSD 0 0 k: 10m * 4.2BSD 0 0 c: 2047973 0 unused 0 0 # raw part, don't edit line 11: partition name out of range a-h: i line 12: partition name out of range a-h: j line 13: partition name out of range a-h: k re-edit the label? [y]: I'm on 8.1-RELEASE. To make use of such feature you need to recreate table with gpart(8). bsdlabel is not going to work. mark...@melon ~ $ sudo dd if=/dev/zero of=myfile.img bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 2.095537 secs (50038530 bytes/sec) mark...@melon ~ $ sudo mdconfig -a -f myfile.img -u 2 mark...@melon ~ $ sudo gpart create -s MBR md2 md2 created mark...@melon ~ $ sudo gpart show md2s1 gpart: No such geom: md2s1. mark...@melon ~ $ sudo gpart add -t freebsd md2 md2s1 added mark...@melon ~ $ sudo gpart add -t freebsd-ufs md2s1 gpart: No such geom: md2s1. mark...@melon ~ $ sudo gpart create -s BSD md2s1 gpart create -s BSD -n 26 md2s1 Thank you, I didn't see this little part of gpart(8). -- Demelier David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8 partitions maximum
On 30/11/2010 23:29, Paul B Mahol wrote: On 11/30/10, David DEMELIERdemelier.da...@gmail.com wrote: 2010/11/30 Paul B Maholone...@gmail.com: On 11/30/10, David DEMELIERdemelier.da...@gmail.com wrote: 2010/11/30 Patrick Lamaizierepatf...@davenulle.org: Le Tue, 30 Nov 2010 21:45:03 +0100, David Demelierdemelier.da...@gmail.com a ecrit : Hello, Hello, We all know that we can only have 8 ufs partitions in one freebsd slice. Since OpenBSD and NetBSD can support at most 32 partitions iirc. I wonder why FreeBSD still lacks more ufs partitions in one slice? Is there any plan to grow up max partitions or every work is dedicated to ZFS? hmmm, isn't already done in 8.X ? from what's cooking for FreeBSD 8.0 http://ivoras.sharanet.org/freebsd/freebsd8.html bsdlabel gets extended to 26 partitions Status: Committed to -CURRENT Will appear in 8.0: sure Author: Marcel Moolenaar Web: commit message bsdlabel is (finally!) extended to support more than 8 partitions. The new limit of 26 partitions comes from the number of lower-case letters. To make use of this change, GEOM_PART needs to be used instead of GEOM_BSD (this is default in 8.0 but will not work with older kernels). I don't have GEOM_PART in my kernel, but if you said it's default it should be pulled in. Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org But why : # /dev/md2s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 10m 164.2BSD0 0 b: 10m *4.2BSD0 0 d: 10m *4.2BSD0 0 e: 10m *4.2BSD0 0 f: 10m *4.2BSD0 0 g: 10m *4.2BSD0 0 h: 10m *4.2BSD0 0 i: 10m *4.2BSD0 0 j: 10m *4.2BSD0 0 k: 10m *4.2BSD0 0 c: 20479730unused0 0 # raw part, don't edit line 11: partition name out of range a-h: i line 12: partition name out of range a-h: j line 13: partition name out of range a-h: k re-edit the label? [y]: I'm on 8.1-RELEASE. To make use of such feature you need to recreate table with gpart(8). bsdlabel is not going to work. mark...@melon ~ $ sudo dd if=/dev/zero of=myfile.img bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 2.095537 secs (50038530 bytes/sec) mark...@melon ~ $ sudo mdconfig -a -f myfile.img -u 2 mark...@melon ~ $ sudo gpart create -s MBR md2 md2 created mark...@melon ~ $ sudo gpart show md2s1 gpart: No such geom: md2s1. mark...@melon ~ $ sudo gpart add -t freebsd md2 md2s1 added mark...@melon ~ $ sudo gpart add -t freebsd-ufs md2s1 gpart: No such geom: md2s1. mark...@melon ~ $ sudo gpart create -s BSD md2s1 gpart create -s BSD -n 26 md2s1 mark...@melon ~ $ sudo gpart create -s BSD -n 26 md0s1 gpart: entries '26': Invalid argument mark...@melon ~ $ sudo gpart create -s BSD -n 8 md0s1 md0s1 created ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a gmirror disappears after adding gjournals to its partitions
CyberLeo Kitsana cyber...@cyberleo.net wrote: ... I hope it makes sense! No problem with the explanation making sense; what I don't follow is the behavior of bsdlabel. Given the way I set it up this drive _should_ contain _two_ labels, but for some unfathomable reason bsdlabel seems to be using the second (inner) one while ignoring the first (outer) one entirely. The device itself is ad0. Its MBR contains a slice table, defining ad0s1 and ad0s2. (ad0s1 is FAT32 and AFAIK need not be considered further at this point.) ad0s2 starts with a bsdlabel, which defines ad0s2a and ad0s2b. (ad0s2b is intended to be used as swap and, like ad0s1, need not be considered further at this point -- but it _should_ be instantiated along with ad0s2a.) ad0s2a is supposed to be the provider for gm0, and it starts with a bsdlabel that is intended to partition gm0 into gm0[ade], but since geom_mirror.ko hasn't been loaded yet gm0 doesn't exist and ad0s2a is just a partition that happens to start with a bsdlabel and end with gmirror metadata. I could understand if bsdlabel tasted ad0s2a, found the label, and (recursively) instantiated ad0s2aa, ad0s2ad, and ad0s2ae; but that doesn't seem to happen. Instead, bsdlabel seems to ignore (or forget) the first label it tasted -- the one on ad0s2 -- and treats the one on ad0s2a as applying to ad0s2. We end up with ad0s2a containing the disk blocks intended for gm0a, ad0s2d containing the disk blocks intended for gm0d, ad0s2e containing the disk blocks intended for gm0e; and the blocks intended for ad0s2b (swap) -- which were not supposed to have been involved with any mirror or journal -- seem to have disappeared entirely. This seems like a bug. Now gjournal gets into the act, consuming the phony ad0s2[ade] before gmirror gets a chance to taste the real ad0s2a and instantiate gm0. That explains why gm0 and /dev/mirror are missing, but not why ad0s2b is missing, nor why we have ad0s2[ade] (and the corresponding .journal's) rather than ad0s2a[ade] (and their .journal's). (This machine is likely too old to understand GPT.) The machine's bios does not need to understand GPT to use it on a pure data disk; only as a boot disk. This is, however, intended as a boot disk -- gm0a, gm0d, and gm0e are supposed to be root, /var, and /usr respectively -- and it does seem to boot OK until it tries find the root FS (because /etc/fstab is set up to use gm0[ade].journal instead of ad0s2[ade].journal). I suppose I could try partitioning ad0s2a with gpt instead of with bsdlabel, but would the loader still be able to find the kernel? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a gmirror disappears after adding gjournals to its partitions
CyberLeo Kitsana cyber...@cyberleo.net wrote: If the kldstat Id numbers are assigned sequentially, it looks as if geom_journal got loaded first and this may somehow be related (although I don't entirely see how -- absent geom_mirror to make gm0 and its partitions visible, I'd think that geom_journal should not be able to find its metadata at all). From what I've found, this is because there is no taste difference between a bsdlabel on a gmirror and a bsdlabel on a non-mirror. ... which seems like a bug, unless I misunderstand how geoms work -- see diagram below: * If gjournal stores its metadata at the end of its provider, it should not be finding anything recognizable at the end of ad0s2a, because that block contains gmirror's metadata. * OTOH, if gjournal is looking for something at the beginning of its provider, it should be finding a bsdlabel -- not gjournal metadata -- at the beginning of ad0s2a and that should keep it from recognizing anything in ad0s2a (which is already known to be a partition, thus finding another bsdlabel at its beginning cannot be legitimate). It looks to me as if gjournal is confused: it claims to have found data and journal on each of ad0s2a, ad0s2d, and ad0s2e but in fact only the first of those even exists! The actual partitioning of ad0s2 is into ad0s2a and ad0s2b (plus the conventional ad0s2c entry covering all of ad0s2). It is gm0 (whose provider is ad0s2a) that is partitioned into gm0a, gm0d, and gm0e; if gm0's bsdlabel were interpreted as being directly on ad0s2a, shouldn't those partitions be named ad0s2aa, ad0s2ad, and ad0s2ae? __ | ad0s2 bsdlabel (on ad0s2) | ad0s2c _ || ad0s2a | gm0 bsdlabel (on gm0) ||| gm0c _ ||| | gm0a | data ||| | | ||| | |_ ||| | | journal ||| | |_ ||| |___|_gjMeta ||| | gm0d | data ||| | | ||| | | ||| | | ||| | | ||| | |_ ||| | | journal ||| | |_ ||| |___|_gjMeta ||| | gm0e | data ||| | | ||| | | ||| | | ||| | | ||| | | ||| | | ||| | | ||| | | ||| | | ||| | | ||| | | ||| | | ||| | |_ ||| | | journal ||| | |_ |||__|___|_gjMeta ||_gmMeta || ad0s2b || || ||_ ... either make the two look different somehow (use a different geom that stores its metadata at the beginning of the provider, instead of the end, thus eliminating ambiguity in the bsdlabel taste), When I asked earlier how to subdivide gm0, bsdlabel was recommended. Is there something else that would work better? (This machine is likely too old to understand GPT.) or to make the inner geom avoid the outer devices (hardcode provider names in metadata). Since you have an outer geom that provides a static name, hardcoding the name of the gmirror into the gjournal metadata shouldn't cause anything to break if your disks change places, either. But I suspect this may not scale well. Suppose I later decide to mirror the swap instead of using ad0s2b and ad8s2b as separate swap partitions. Is there not a 50/50 chance of the swap mirror becoming gm0 and my current gm0 becoming gm1, thereby breaking any metadata that depends on hard-coded provider names? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a gmirror disappears after adding gjournals to its partitions
On 11/24/2010 04:52 AM, per...@pluto.rain.com wrote: It looks to me as if gjournal is confused: It is not gjournal that is confused; it's bsdlabel. The gjournals lie entirely within the partitions defined within the bsdlabel, and don't care about anything outside of that. The ambiguity here is that the bsdlabel is stored at the beginning of the disk, and is very loose about what it accepts as valid, since there is no direct harm in being eager. The metadata for gmirror is stored at the end. The metadata for the bsdlabel is stored at the beginning. When bsdlabel tastes before gmirror, it sees the same label on the component disks that would be on the gm0 mirror. Moreover, all the partitions it then creates are identically sized, and contain exactly the same data, as they would on the mirror. It will complain that partition 'c' doesn't cover the whole unit, but this is not a fatal error as it doesn't take exclusive access, and so you are always free to use that same bsdlabel through another geom path. The problem arises when bsdlabel tastes ad0 before gmirror, and creates all the partitions thereupon, which triggers a taste of all the newly created devices by gjournal, which opens the devices exclusively once it finds the metadata it needs within the partitions. Now that they're opened exclusively somewhere, all the other paths to that device through the geom graph are withered, and cannot be tasted or used by anything else, including gmirror. Hardcoding provider names into gjournal makes it reject these ambiguously created devices. Since gjournal doesn't take exclusive access, gmirror can now taste the still-available ad0, see that it's a mirror, and launch gm0, which triggers a taste by bsdlabel (and creates the partitions) which triggers a taste by gjournal, which matches the names its expecting. That was difficult to keep clear. I hope it makes sense! ... either make the two look different somehow (use a different geom that stores its metadata at the beginning of the provider, instead of the end, thus eliminating ambiguity in the bsdlabel taste), When I asked earlier how to subdivide gm0, bsdlabel was recommended. Is there something else that would work better? (This machine is likely too old to understand GPT.) The machine's bios does not need to understand GPT to use it on a pure data disk; only as a boot disk. There are a few bioses that throw fits when not all the disks include mbr/slice tables, but those (thankfully) tend to be the minority. Plus, since GPT expects metadata at both the beginning and end of the disk, seeing gmirror metadata instead may prevent it from creating these ambiguous device nodes as well (but test this assumption before relying on it). or to make the inner geom avoid the outer devices (hardcode provider names in metadata). Since you have an outer geom that provides a static name, hardcoding the name of the gmirror into the gjournal metadata shouldn't cause anything to break if your disks change places, either. But I suspect this may not scale well. Suppose I later decide to mirror the swap instead of using ad0s2b and ad8s2b as separate swap partitions. Is there not a 50/50 chance of the swap mirror becoming gm0 and my current gm0 becoming gm1, thereby breaking any metadata that depends on hard-coded provider names? When you create a mirror, you give it an explicit name, which will not change over the life of the mirror without your explicit action. This name does not have to be 'gm0' or some such. I have named mirrors after the hostname, or 'hostname-purpose', such as 'sc1425-root' and 'sc1425-swap' -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net cyber...@cyberleo.net Furry Peace! - http://.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a gmirror disappears after adding gjournals to its partitions
On 11/22/2010 10:19 PM, per...@pluto.rain.com wrote: krad kra...@gmail.com wrote: On 21 November 2010 06:10, per...@pluto.rain.com wrote: ... manually-created config files, while still in chroot after install Fixit# cat /boot/loader.conf geom_mirror_load=YES geom_journal_load=YES vfs.root.mountfrom=ufs:/dev/mirror/gm0a.journal vfs.root.mountfrom.options=rw ... output from kldstat, after booting the newly-installed system -- and manually mounting the root FS -- showing that geom_mirror.ko did get loaded. Id Refs AddressSize Name 16 0xc040 bb5504 kernel 21 0xc0fb6000 14540geom_journal.ko 31 0xc0fcb000 16ed4geom_mirror.ko ... sounds silly but are you loading the gmirror kernel module via loader.conf Yes, I'm even setting geom_mirror_load to YES before setting geom_journal_load to YES (although I doubt the order of these settings in loader.conf makes any difference). If the kldstat Id numbers are assigned sequentially, it looks as if geom_journal got loaded first and this may somehow be related (although I don't entirely see how -- absent geom_mirror to make gm0 and its partitions visible, I'd think that geom_journal should not be able to find its metadata at all). From what I've found, this is because there is no taste difference between a bsdlabel on a gmirror and a bsdlabel on a non-mirror. Since both gmirror and gjournal are greedy (they take exclusive access of their parent providers upon successful taste, and not upon exclusive access to their own providers like glabel), the first one to successfully taste and start is the winner; the other will never get to taste those devices. The trick here is to either make the two look different somehow (use a different geom that stores its metadata at the beginning of the provider, instead of the end, thus eliminating ambiguity in the bsdlabel taste), or to make the inner geom avoid the outer devices (hardcode provider names in metadata). Since you have an outer geom that provides a static name, hardcoding the name of the gmirror into the gjournal metadata shouldn't cause anything to break if your disks change places, either. http://pb.cyberleo.net/?show=m7fcbcef7 -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net cyber...@cyberleo.net Furry Peace! - http://.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a gmirror disappears after adding gjournals to its partitions
2010/11/23 CyberLeo Kitsana cyber...@cyberleo.net On 11/22/2010 10:19 PM, per...@pluto.rain.com wrote: krad kra...@gmail.com wrote: On 21 November 2010 06:10, per...@pluto.rain.com wrote: ... manually-created config files, while still in chroot after install Fixit# cat /boot/loader.conf geom_mirror_load=YES geom_journal_load=YES vfs.root.mountfrom=ufs:/dev/mirror/gm0a.journal vfs.root.mountfrom.options=rw ... output from kldstat, after booting the newly-installed system -- and manually mounting the root FS -- showing that geom_mirror.ko did get loaded. Id Refs AddressSize Name 16 0xc040 bb5504 kernel 21 0xc0fb6000 14540geom_journal.ko 31 0xc0fcb000 16ed4geom_mirror.ko ... sounds silly but are you loading the gmirror kernel module via loader.conf Yes, I'm even setting geom_mirror_load to YES before setting geom_journal_load to YES (although I doubt the order of these settings in loader.conf makes any difference). If the kldstat Id numbers are assigned sequentially, it looks as if geom_journal got loaded first and this may somehow be related (although I don't entirely see how -- absent geom_mirror to make gm0 and its partitions visible, I'd think that geom_journal should not be able to find its metadata at all). From what I've found, this is because there is no taste difference between a bsdlabel on a gmirror and a bsdlabel on a non-mirror. Since both gmirror and gjournal are greedy (they take exclusive access of their parent providers upon successful taste, and not upon exclusive access to their own providers like glabel), the first one to successfully taste and start is the winner; the other will never get to taste those devices. The trick here is to either make the two look different somehow (use a different geom that stores its metadata at the beginning of the provider, instead of the end, thus eliminating ambiguity in the bsdlabel taste), or to make the inner geom avoid the outer devices (hardcode provider names in metadata). Since you have an outer geom that provides a static name, hardcoding the name of the gmirror into the gjournal metadata shouldn't cause anything to break if your disks change places, either. http://pb.cyberleo.net/?show=m7fcbcef7 -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net cyber...@cyberleo.net Furry Peace! - http://.fur.com/peace/ I think what he is saying is slice it up 1st, then mirror the slices, and slap the journal on top of that ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: a gmirror disappears after adding gjournals to its partitions
On 21 November 2010 06:10, per...@pluto.rain.com wrote: Is there something wrong with this sequence, in Fixit: * create a mirror * partition it with disklabel * create journals on the partitions * install * reboot? After rebooting, the mirror had disappeared and the journals seemed to exist directly on partitions of the mirror's provider rather than on the mirror itself. Details: Using Fixit# from the 8.1-RELEASE memstick I defined a gmirror (initially containing only one provider; the other to be added later), partitioned it using disklabel, added a journal to each of the partitions, ran newfs -J on them, and installed FreeBSD using http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror as a guide (with a few differences due to this installation being UFS rather than ZFS). In Fixit the /dev tree contained entries for both the mirror and the journal devices, but when I rebooted the mirror did not show up -- even though geom_mirror.ko was loaded. What would cause this sort of mixup, and how do I fix it? Is any more info needed? contents of /dev/mirror before creating the journals Fixit# ls -la /dev/mirror total 1 dr-xr-xr-x 2 root 0 512 Nov 14 00:17 . dr-xr-xr-x 9 root 0 512 Nov 14 00:11 .. crw-r- 1 root operator0, 80 Nov 14 00:36 gm0 crw-r- 1 root operator0, 126 Nov 14 00:36 gm0a crw-r- 1 root operator0, 128 Nov 14 00:36 gm0d crw-r- 1 root operator0, 129 Nov 14 00:36 gm0e corresponding disklabel report Fixit# disklabel /dev/mirror/gm0 # /dev/mirror/gm0: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 8388608 164.2BSD 1024 819216 c: 6199075170unused0 0 d: 25165824 83886244.2BSD0 0 0 e: 586353069 335544484.2BSD0 0 0 journal creation, with resulting dmesg reports Fixit# gjournal label -s 2G /dev/mirror/gm0a GEOM_JOURNAL: Journal 1098378706: mirror/gm0a contains data. GEOM_JOURNAL: Journal 1098378706: mirror/gm0a contains journal. GEOM_JOURNAL: Journal mirror/gm0a clean. Fixit# gjournal label -s 2G /dev/mirror/gm0d GEOM_JOURNAL: Journal 3795372090: mirror/gm0d contains data. GEOM_JOURNAL: Journal 3795372090: mirror/gm0d contains journal. GEOM_JOURNAL: Journal mirror/gm0d clean. Fixit# gjournal label -s 2G /dev/mirror/gm0e GEOM_JOURNAL: Journal 2063379813: mirror/gm0e contains data. GEOM_JOURNAL: Journal 2063379813: mirror/gm0e contains journal. GEOM_JOURNAL: Journal mirror/gm0e clean. contents of /dev/mirror after creating the journals Fixit# ls -la /dev/mirror total 1 dr-xr-xr-x 2 root 0 512 Nov 14 00:17 ./ dr-xr-xr-x 9 root 0 512 Nov 14 00:11 ../ crw-r- 1 root operator0, 80 Nov 14 02:01 gm0 crw-r- 1 root operator0, 78 Nov 14 02:06 gm0a crw-r- 1 root operator0, 126 Nov 14 02:06 gm0a.journal crw-r- 1 root operator0, 125 Nov 14 02:07 gm0d crw-r- 1 root operator0, 128 Nov 14 02:07 gm0d.journal crw-r- 1 root operator0, 130 Nov 14 02:07 gm0e crw-r- 1 root operator0, 129 Nov 14 02:07 gm0e.journal newfs commands Fixit# newfs -J /dev/mirror/gm0a.journal Fixit# newfs -J /dev/mirror/gm0d.journal Fixit# newfs -J /dev/mirror/gm0e.journal mount the resulting filesystems (and one ordinary partition, neither mirrored nor journalled, to be used as /tmp -- I figure /tmp is expendable), resulting in this FS configuration Fixit# mount /dev/md0 on / (ufs, local) devfs on /dev (devfs, local, multilabel) /dev/da1a on /dist (ufs, local, read-only) /dev/mirror/gm0a.journal on /mnt (ufs, local, gjournal) /dev/ad8s2d on /mnt/tmp (ufs, local) /dev/mirror/gm0d.journal on /mnt/var (ufs, local, gjournal) /dev/mirror/gm0e.journal on /mnt/usr (ufs, local, gjournal) install per http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror, no detailed log kept manually-created config files, while still in chroot after install Fixit# cat /boot/loader.conf geom_mirror_load=YES geom_journal_load=YES vfs.root.mountfrom=ufs:/dev/mirror/gm0a.journal vfs.root.mountfrom.options=rw Fixit# cat /etc/fstab /dev/mirror/gm0a.journal / ufs rw 0 1 /dev/ad0s2b none swapsw 0 0 /dev/ad8s2b none swapsw 0 0 /dev/ad8s2d /tmp ufs rw 0 2 /dev/mirror/gm0d.journal /var ufs rw 0 3 /dev/mirror/gm0e.journal /usr ufs rw 0 4 /dev/da1a/dist ufs ro 0 0 devfs/dev devfs multilabel 0 0 output from kldstat, after booting the newly-installed system -- and manually mounting the root FS -- showing that geom_mirror.ko did get loaded. Id Refs
Re: a gmirror disappears after adding gjournals to its partitions
krad kra...@gmail.com wrote: On 21 November 2010 06:10, per...@pluto.rain.com wrote: ... manually-created config files, while still in chroot after install Fixit# cat /boot/loader.conf geom_mirror_load=YES geom_journal_load=YES vfs.root.mountfrom=ufs:/dev/mirror/gm0a.journal vfs.root.mountfrom.options=rw ... output from kldstat, after booting the newly-installed system -- and manually mounting the root FS -- showing that geom_mirror.ko did get loaded. Id Refs AddressSize Name 16 0xc040 bb5504 kernel 21 0xc0fb6000 14540geom_journal.ko 31 0xc0fcb000 16ed4geom_mirror.ko ... sounds silly but are you loading the gmirror kernel module via loader.conf Yes, I'm even setting geom_mirror_load to YES before setting geom_journal_load to YES (although I doubt the order of these settings in loader.conf makes any difference). If the kldstat Id numbers are assigned sequentially, it looks as if geom_journal got loaded first and this may somehow be related (although I don't entirely see how -- absent geom_mirror to make gm0 and its partitions visible, I'd think that geom_journal should not be able to find its metadata at all). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
a gmirror disappears after adding gjournals to its partitions
Is there something wrong with this sequence, in Fixit: * create a mirror * partition it with disklabel * create journals on the partitions * install * reboot? After rebooting, the mirror had disappeared and the journals seemed to exist directly on partitions of the mirror's provider rather than on the mirror itself. Details: Using Fixit# from the 8.1-RELEASE memstick I defined a gmirror (initially containing only one provider; the other to be added later), partitioned it using disklabel, added a journal to each of the partitions, ran newfs -J on them, and installed FreeBSD using http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror as a guide (with a few differences due to this installation being UFS rather than ZFS). In Fixit the /dev tree contained entries for both the mirror and the journal devices, but when I rebooted the mirror did not show up -- even though geom_mirror.ko was loaded. What would cause this sort of mixup, and how do I fix it? Is any more info needed? contents of /dev/mirror before creating the journals Fixit# ls -la /dev/mirror total 1 dr-xr-xr-x 2 root 0 512 Nov 14 00:17 . dr-xr-xr-x 9 root 0 512 Nov 14 00:11 .. crw-r- 1 root operator0, 80 Nov 14 00:36 gm0 crw-r- 1 root operator0, 126 Nov 14 00:36 gm0a crw-r- 1 root operator0, 128 Nov 14 00:36 gm0d crw-r- 1 root operator0, 129 Nov 14 00:36 gm0e corresponding disklabel report Fixit# disklabel /dev/mirror/gm0 # /dev/mirror/gm0: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 8388608 164.2BSD 1024 819216 c: 6199075170unused0 0 d: 25165824 83886244.2BSD0 0 0 e: 586353069 335544484.2BSD0 0 0 journal creation, with resulting dmesg reports Fixit# gjournal label -s 2G /dev/mirror/gm0a GEOM_JOURNAL: Journal 1098378706: mirror/gm0a contains data. GEOM_JOURNAL: Journal 1098378706: mirror/gm0a contains journal. GEOM_JOURNAL: Journal mirror/gm0a clean. Fixit# gjournal label -s 2G /dev/mirror/gm0d GEOM_JOURNAL: Journal 3795372090: mirror/gm0d contains data. GEOM_JOURNAL: Journal 3795372090: mirror/gm0d contains journal. GEOM_JOURNAL: Journal mirror/gm0d clean. Fixit# gjournal label -s 2G /dev/mirror/gm0e GEOM_JOURNAL: Journal 2063379813: mirror/gm0e contains data. GEOM_JOURNAL: Journal 2063379813: mirror/gm0e contains journal. GEOM_JOURNAL: Journal mirror/gm0e clean. contents of /dev/mirror after creating the journals Fixit# ls -la /dev/mirror total 1 dr-xr-xr-x 2 root 0 512 Nov 14 00:17 ./ dr-xr-xr-x 9 root 0 512 Nov 14 00:11 ../ crw-r- 1 root operator0, 80 Nov 14 02:01 gm0 crw-r- 1 root operator0, 78 Nov 14 02:06 gm0a crw-r- 1 root operator0, 126 Nov 14 02:06 gm0a.journal crw-r- 1 root operator0, 125 Nov 14 02:07 gm0d crw-r- 1 root operator0, 128 Nov 14 02:07 gm0d.journal crw-r- 1 root operator0, 130 Nov 14 02:07 gm0e crw-r- 1 root operator0, 129 Nov 14 02:07 gm0e.journal newfs commands Fixit# newfs -J /dev/mirror/gm0a.journal Fixit# newfs -J /dev/mirror/gm0d.journal Fixit# newfs -J /dev/mirror/gm0e.journal mount the resulting filesystems (and one ordinary partition, neither mirrored nor journalled, to be used as /tmp -- I figure /tmp is expendable), resulting in this FS configuration Fixit# mount /dev/md0 on / (ufs, local) devfs on /dev (devfs, local, multilabel) /dev/da1a on /dist (ufs, local, read-only) /dev/mirror/gm0a.journal on /mnt (ufs, local, gjournal) /dev/ad8s2d on /mnt/tmp (ufs, local) /dev/mirror/gm0d.journal on /mnt/var (ufs, local, gjournal) /dev/mirror/gm0e.journal on /mnt/usr (ufs, local, gjournal) install per http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror, no detailed log kept manually-created config files, while still in chroot after install Fixit# cat /boot/loader.conf geom_mirror_load=YES geom_journal_load=YES vfs.root.mountfrom=ufs:/dev/mirror/gm0a.journal vfs.root.mountfrom.options=rw Fixit# cat /etc/fstab /dev/mirror/gm0a.journal / ufs rw 0 1 /dev/ad0s2b none swapsw 0 0 /dev/ad8s2b none swapsw 0 0 /dev/ad8s2d /tmp ufs rw 0 2 /dev/mirror/gm0d.journal /var ufs rw 0 3 /dev/mirror/gm0e.journal /usr ufs rw 0 4 /dev/da1a/dist ufs ro 0 0 devfs/dev devfs multilabel 0 0 output from kldstat, after booting the newly-installed system -- and manually mounting the root FS -- showing that geom_mirror.ko did get loaded. Id Refs AddressSize Name 16 0xc040 bb5504 kernel 21 0xc0fb6000 14540geom_journal.ko 31 0xc0fcb000 16ed4geom_mirror.ko dmesg
nanobsd upgrade partitions
Hello, Could someone advise how one should create 1 unused partition for upgrading nanobsd in myconf.nano? What variables should I put into the config file to have a such? How big it should be for 4GB card? Also what is the filesystem referred by NANO_DATASIZE variable? Thanks in advance! Dimitar ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: nanobsd upgrade partitions
Dnia poniedziałek, 17 maja 2010 o 10:06:05 Dimitar Vassilev napisał(a): Hello, Could someone advise how one should create 1 unused partition for upgrading nanobsd in myconf.nano? What variables should I put into the config file to have a such? # Number of code images on media (1 or 2) NANO_IMAGES=2 This should do it for you. It does it automaticaly to create two images of the same size. How big it should be for 4GB card? It depends on your needs. How much you need for your nanobsd installation. Check how big it is now and add some space for future. If you will leave enough room you won't need to reflash full disk but only image of one partition/slice. Also what is the filesystem referred by NANO_DATASIZE variable? If I remember correctly DATASIZE is size of additional partition f.ex. for application data that remains untouched between upgrading of nanobsd. Thanks in advance! Dimitar Greetings, Maciej Milewski ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: nanobsd upgrade partitions
Dzienki Maciej :-) 2010/5/17 Maciej Milewski m...@dat.pl: Dnia poniedziałek, 17 maja 2010 o 10:06:05 Dimitar Vassilev napisał(a): Hello, Could someone advise how one should create 1 unused partition for upgrading nanobsd in myconf.nano? What variables should I put into the config file to have a such? # Number of code images on media (1 or 2) NANO_IMAGES=2 This should do it for you. It does it automaticaly to create two images of the same size. How big it should be for 4GB card? It depends on your needs. How much you need for your nanobsd installation. Check how big it is now and add some space for future. If you will leave enough room you won't need to reflash full disk but only image of one partition/slice. Also what is the filesystem referred by NANO_DATASIZE variable? If I remember correctly DATASIZE is size of additional partition f.ex. for application data that remains untouched between upgrading of nanobsd. Thanks in advance! Dimitar Greetings, Maciej Milewski ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: More than 8 partitions
2010/5/2 Christopher Key cj...@cam.ac.uk Jon Theil Nielsen wrote: 2010/5/1 Christopher Key cj...@cam.ac.uk Jon Theil Nielsen wrote: Hi I'm running 8.0-Release on an external usb hard drive. and have dual-boot with FreeBSD on da0s2 and Windows XP on da0s1. I made a setup via Sysinstall with 7 partitions: /dev/da0s2a on / (ufs, local) /dev/da0s2b (swap) /dev/da0s2d on /var (ufs, local, soft-updates) /dev/da0s2e on /tmp (ufs, local, soft-updates) /dev/da0s2f on /usr (ufs, local, soft-updates) /dev/da0s2h on /var/log (ufs, local, soft-updates) /dev/da0s2g on /home (ufs, local, soft-updates) I have about 660 GB left unused on da0s2 that I would like to use for backups. But I can't figure out how to create one more partition. If i create a file for bsdlabel like # sizeoffset fstype i: * 0 4.2BSD I get the following error message: line 2: partition name out of range a-h: i I have also tried with gpart: gpart add -s 500G -t freebsd -f x da0s2 I get something like gpart: index '9': No space left on device I thought that 8.0 should support more than 8 partitions. Maybe it does, but then I don't know how to do. Any ideas? I believe that FreeBSD does support more than 8 partitions on a disk (apparently up to 20 using gpart), but that you need sufficient entries for these partitions to be created in the disklabel, viz. gpart create -n 20 ... Some testing seems to indicate that you can manually override this by changing by byte 0x28a of the disk from 0x08 to 0x14, and that bsdlabel / gpart will then allow you to create further partitions on the disk. Kind regards, Christopher Key Thanks Christopher I am not sure if I understand all of if. And I wouldn't like to wipe the drive to test if is possible to mass produce partitions like that. Could be useful in another situation, though. My knowlodge of GEOM and its utilities is very limited. Since I have succeded in creating the two slices with fdisk and subsequently populate them with bsdlabel, my only problem is how to create the last partition from the unpartioned space on da0s2. As mentioned in the beginning of this post, I have tried with both bsdlabel (from a file) and by issuing the gpart add command. With no luck. Would it be any help to give more specific about the drive/slice? The output of df -h | grep dev/da0 is: /dev/da0s2a 3.9G 630M2.9G17%/ /dev/da0s2g97G 160K 89G 0%/home /dev/da0s2e 3.9G 129M3.4G 4%/tmp /dev/da0s2f48G 6.6G 38G15%/usr /dev/da0s2d 9.7G 151M8.8G 2%/var /dev/da0s2h 3.9G 1.5M3.6G 0%/var/log and of gpart show da0: = 0 1759551255 da0s2 BSD (839G) 0 1048576 - free - (512M) 1048576 8318064 2 freebsd-swap (4.0G) 9366640 7303168 - free - (3.5G) 16669808 8388608 1 freebsd-ufs (4.0G) 2505841620971520 4 freebsd-ufs (10G) 46029936 8388608 5 freebsd-ufs (4.0G) 54418544 104857600 6 freebsd-ufs (50G) 159276144 209715200 7 freebsd-ufs (100G) 936891344 8388608 8 freebsd-ufs (4.0G) 377379952 1382171303 - free - (659G) and, finaly, of bsdlabel da0s2: # /dev/da0s2: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a:8388608 166698084.2BSD0 0 0 b:83180641048576 swap c: 1759551255 0unused0 0 # raw part, don't edit d: 20971520 250584164.2BSD0 0 0 e:8388608 460299364.2BSD0 0 0 f: 104857600 544185444.2BSD0 0 0 g: 209715200 1592761444.2BSD0 0 0 h:8388608 3689913444.2BSD0 0 0 In my desparate effort to understand these informations/data, i have put them into a spreadsheet and rearranged them - including some of my own calculations and assumptions. bsdlabel output - sorted by sector offset: #size offset (GB*) c 1.759.551.2550839 b 8.318.0641.048.576 4 a 8.388.608 16.669.808 4 d 20.971.520 25.058.416 10 e 8.388.608 46.029.936 4 f 104.857.600 54.418.544 50 g 209.715.200 159.276.144100 h 8.388.608 368.991.344 4 gpart show output - sorted by sector offset: (#) (size)(offset) (GB) (offset*) (GiB*)(i) 1.048.57600,5 01 free b 8.318.0641.048.576 4 1.048.5764 2 7.303.1689.366.6403,5 9.366.6403 free a 8.388.608 16.669.808 4
Re: More than 8 partitions
On 2010/5/2, Christopher Key cj...@cam.ac.uk wrote: frhed. Next write the data back to the disk: dd if=/tmp/hdr of=/dev/da0s2 On 2010/5/12, Jon Theil Nielsen wrote: obviously this is not the case. So I'll dd the existing partitions to another drive, use gpart to create enough partitions and then dd the old content back. I could easily use a standard disk layout, but the other approach will add some to my FreeBSD knowledge.. Just pointing out a rabbit hole here . . . You should be aware, too that if you want to _change_ the size (or any of several other params) of the filesystem, you don't really want dd, you want to dump(8) the filesystem and then use restore(8) -- as the man page says, this is the only reliable way to change various filesystem params. Using dd will be fine only if the sizes and all other params are to be identical (which is the case in Chris' comment, but not in the general case). Andrew. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: More than 8 partitions
2010/5/12 A. Wright and...@qemg.org On 2010/5/2, Christopher Key cj...@cam.ac.uk wrote: frhed. Next write the data back to the disk: dd if=/tmp/hdr of=/dev/da0s2 On 2010/5/12, Jon Theil Nielsen wrote: obviously this is not the case. So I'll dd the existing partitions to another drive, use gpart to create enough partitions and then dd the old content back. I could easily use a standard disk layout, but the other approach will add some to my FreeBSD knowledge.. Just pointing out a rabbit hole here . . . You should be aware, too that if you want to _change_ the size (or any of several other params) of the filesystem, you don't really want dd, you want to dump(8) the filesystem and then use restore(8) -- as the man page says, this is the only reliable way to change various filesystem params. Using dd will be fine only if the sizes and all other params are to be identical (which is the case in Chris' comment, but not in the general case). Andrew. Thanks again That was a very good point. I think I'll wait until tomorrow. But I'll get back here if I run into troubles. :-I Regards, Jon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: More than 8 partitions
Jon Theil Nielsen wrote: 2010/5/1 Christopher Key cj...@cam.ac.uk Jon Theil Nielsen wrote: Hi I'm running 8.0-Release on an external usb hard drive. and have dual-boot with FreeBSD on da0s2 and Windows XP on da0s1. I made a setup via Sysinstall with 7 partitions: /dev/da0s2a on / (ufs, local) /dev/da0s2b (swap) /dev/da0s2d on /var (ufs, local, soft-updates) /dev/da0s2e on /tmp (ufs, local, soft-updates) /dev/da0s2f on /usr (ufs, local, soft-updates) /dev/da0s2h on /var/log (ufs, local, soft-updates) /dev/da0s2g on /home (ufs, local, soft-updates) I have about 660 GB left unused on da0s2 that I would like to use for backups. But I can't figure out how to create one more partition. If i create a file for bsdlabel like # sizeoffset fstype i: * 0 4.2BSD I get the following error message: line 2: partition name out of range a-h: i I have also tried with gpart: gpart add -s 500G -t freebsd -f x da0s2 I get something like gpart: index '9': No space left on device I thought that 8.0 should support more than 8 partitions. Maybe it does, but then I don't know how to do. Any ideas? I believe that FreeBSD does support more than 8 partitions on a disk (apparently up to 20 using gpart), but that you need sufficient entries for these partitions to be created in the disklabel, viz. gpart create -n 20 ... Some testing seems to indicate that you can manually override this by changing by byte 0x28a of the disk from 0x08 to 0x14, and that bsdlabel / gpart will then allow you to create further partitions on the disk. Kind regards, Christopher Key Thanks Christopher I am not sure if I understand all of if. And I wouldn't like to wipe the drive to test if is possible to mass produce partitions like that. Could be useful in another situation, though. My knowlodge of GEOM and its utilities is very limited. Since I have succeded in creating the two slices with fdisk and subsequently populate them with bsdlabel, my only problem is how to create the last partition from the unpartioned space on da0s2. As mentioned in the beginning of this post, I have tried with both bsdlabel (from a file) and by issuing the gpart add command. With no luck. Would it be any help to give more specific about the drive/slice? The output of df -h | grep dev/da0 is: /dev/da0s2a 3.9G 630M2.9G17%/ /dev/da0s2g97G 160K 89G 0%/home /dev/da0s2e 3.9G 129M3.4G 4%/tmp /dev/da0s2f48G 6.6G 38G15%/usr /dev/da0s2d 9.7G 151M8.8G 2%/var /dev/da0s2h 3.9G 1.5M3.6G 0%/var/log and of gpart show da0: = 0 1759551255 da0s2 BSD (839G) 0 1048576 - free - (512M) 1048576 8318064 2 freebsd-swap (4.0G) 9366640 7303168 - free - (3.5G) 16669808 8388608 1 freebsd-ufs (4.0G) 2505841620971520 4 freebsd-ufs (10G) 46029936 8388608 5 freebsd-ufs (4.0G) 54418544 104857600 6 freebsd-ufs (50G) 159276144 209715200 7 freebsd-ufs (100G) 936891344 8388608 8 freebsd-ufs (4.0G) 377379952 1382171303 - free - (659G) and, finaly, of bsdlabel da0s2: # /dev/da0s2: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a:8388608 166698084.2BSD0 0 0 b:83180641048576 swap c: 1759551255 0unused0 0 # raw part, don't edit d: 20971520 250584164.2BSD0 0 0 e:8388608 460299364.2BSD0 0 0 f: 104857600 544185444.2BSD0 0 0 g: 209715200 1592761444.2BSD0 0 0 h:8388608 3689913444.2BSD0 0 0 In my desparate effort to understand these informations/data, i have put them into a spreadsheet and rearranged them - including some of my own calculations and assumptions. bsdlabel output - sorted by sector offset: #size offset (GB*) c 1.759.551.2550839 b 8.318.0641.048.576 4 a 8.388.608 16.669.808 4 d 20.971.520 25.058.416 10 e 8.388.608 46.029.936 4 f 104.857.600 54.418.544 50 g 209.715.200 159.276.144100 h 8.388.608 368.991.344 4 gpart show output - sorted by sector offset: (#) (size)(offset) (GB) (offset*) (GiB*)(i) 1.048.57600,5 01 free b 8.318.0641.048.576 4 1.048.5764 2 7.303.1689.366.6403,5 9.366.6403 free a 8.388.608 16.669.808 4 16.669.8084 1 d 20.971.520 25.058.416 10 25.058.416 10 4 e 8.388.608 46.029.936 4
Re: More than 8 partitions
Jon Theil Nielsen wrote: Hi I'm running 8.0-Release on an external usb hard drive. and have dual-boot with FreeBSD on da0s2 and Windows XP on da0s1. I made a setup via Sysinstall with 7 partitions: /dev/da0s2a on / (ufs, local) /dev/da0s2b (swap) /dev/da0s2d on /var (ufs, local, soft-updates) /dev/da0s2e on /tmp (ufs, local, soft-updates) /dev/da0s2f on /usr (ufs, local, soft-updates) /dev/da0s2h on /var/log (ufs, local, soft-updates) /dev/da0s2g on /home (ufs, local, soft-updates) I have about 660 GB left unused on da0s2 that I would like to use for backups. But I can't figure out how to create one more partition. If i create a file for bsdlabel like # sizeoffset fstype i: * 0 4.2BSD I get the following error message: line 2: partition name out of range a-h: i I have also tried with gpart: gpart add -s 500G -t freebsd -f x da0s2 I get something like gpart: index '9': No space left on device I thought that 8.0 should support more than 8 partitions. Maybe it does, but then I don't know how to do. Any ideas? I believe that FreeBSD does support more than 8 partitions on a disk (apparently up to 20 using gpart), but that you need sufficient entries for these partitions to be created in the disklabel, viz. gpart create -n 20 ... Some testing seems to indicate that you can manually override this by changing by byte 0x28a of the disk from 0x08 to 0x14, and that bsdlabel / gpart will then allow you to create further partitions on the disk. Kind regards, Christopher Key ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: More than 8 partitions
On Fri, 2010-04-30 at 19:44 +0200, Jon Theil Nielsen wrote: Hi I'm running 8.0-Release on an external usb hard drive. and have dual-boot with FreeBSD on da0s2 and Windows XP on da0s1. I made a setup via Sysinstall with 7 partitions: /dev/da0s2a on / (ufs, local) /dev/da0s2b (swap) /dev/da0s2d on /var (ufs, local, soft-updates) /dev/da0s2e on /tmp (ufs, local, soft-updates) /dev/da0s2f on /usr (ufs, local, soft-updates) /dev/da0s2h on /var/log (ufs, local, soft-updates) /dev/da0s2g on /home (ufs, local, soft-updates) I have about 660 GB left unused on da0s2 that I would like to use for backups. But I can't figure out how to create one more partition. If i create a file for bsdlabel like # sizeoffset fstype i: * 0 4.2BSD I get the following error message: line 2: partition name out of range a-h: i I have also tried with gpart: gpart add -s 500G -t freebsd -f x da0s2 I get something like gpart: index '9': No space left on device I thought that 8.0 should support more than 8 partitions. Maybe it does, but then I don't know how to do. Any ideas? Use vinum - thats what I needed to do. Mind I had around 15 partitions to work out so it is effective... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: More than 8 partitions
2010/5/1 Christopher Key cj...@cam.ac.uk Jon Theil Nielsen wrote: Hi I'm running 8.0-Release on an external usb hard drive. and have dual-boot with FreeBSD on da0s2 and Windows XP on da0s1. I made a setup via Sysinstall with 7 partitions: /dev/da0s2a on / (ufs, local) /dev/da0s2b (swap) /dev/da0s2d on /var (ufs, local, soft-updates) /dev/da0s2e on /tmp (ufs, local, soft-updates) /dev/da0s2f on /usr (ufs, local, soft-updates) /dev/da0s2h on /var/log (ufs, local, soft-updates) /dev/da0s2g on /home (ufs, local, soft-updates) I have about 660 GB left unused on da0s2 that I would like to use for backups. But I can't figure out how to create one more partition. If i create a file for bsdlabel like # sizeoffset fstype i: * 0 4.2BSD I get the following error message: line 2: partition name out of range a-h: i I have also tried with gpart: gpart add -s 500G -t freebsd -f x da0s2 I get something like gpart: index '9': No space left on device I thought that 8.0 should support more than 8 partitions. Maybe it does, but then I don't know how to do. Any ideas? I believe that FreeBSD does support more than 8 partitions on a disk (apparently up to 20 using gpart), but that you need sufficient entries for these partitions to be created in the disklabel, viz. gpart create -n 20 ... Some testing seems to indicate that you can manually override this by changing by byte 0x28a of the disk from 0x08 to 0x14, and that bsdlabel / gpart will then allow you to create further partitions on the disk. Kind regards, Christopher Key Thanks Christopher I am not sure if I understand all of if. And I wouldn't like to wipe the drive to test if is possible to mass produce partitions like that. Could be useful in another situation, though. My knowlodge of GEOM and its utilities is very limited. Since I have succeded in creating the two slices with fdisk and subsequently populate them with bsdlabel, my only problem is how to create the last partition from the unpartioned space on da0s2. As mentioned in the beginning of this post, I have tried with both bsdlabel (from a file) and by issuing the gpart add command. With no luck. Would it be any help to give more specific about the drive/slice? The output of df -h | grep dev/da0 is: /dev/da0s2a 3.9G 630M2.9G17%/ /dev/da0s2g97G 160K 89G 0%/home /dev/da0s2e 3.9G 129M3.4G 4%/tmp /dev/da0s2f48G 6.6G 38G15%/usr /dev/da0s2d 9.7G 151M8.8G 2%/var /dev/da0s2h 3.9G 1.5M3.6G 0%/var/log and of gpart show da0: = 0 1759551255 da0s2 BSD (839G) 0 1048576 - free - (512M) 1048576 8318064 2 freebsd-swap (4.0G) 9366640 7303168 - free - (3.5G) 16669808 8388608 1 freebsd-ufs (4.0G) 2505841620971520 4 freebsd-ufs (10G) 46029936 8388608 5 freebsd-ufs (4.0G) 54418544 104857600 6 freebsd-ufs (50G) 159276144 209715200 7 freebsd-ufs (100G) 936891344 8388608 8 freebsd-ufs (4.0G) 377379952 1382171303 - free - (659G) and, finaly, of bsdlabel da0s2: # /dev/da0s2: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a:8388608 166698084.2BSD0 0 0 b:83180641048576 swap c: 1759551255 0unused0 0 # raw part, don't edit d: 20971520 250584164.2BSD0 0 0 e:8388608 460299364.2BSD0 0 0 f: 104857600 544185444.2BSD0 0 0 g: 209715200 1592761444.2BSD0 0 0 h:8388608 3689913444.2BSD0 0 0 In my desparate effort to understand these informations/data, i have put them into a spreadsheet and rearranged them - including some of my own calculations and assumptions. bsdlabel output - sorted by sector offset: #size offset (GB*) c 1.759.551.2550839 b 8.318.0641.048.576 4 a 8.388.608 16.669.808 4 d 20.971.520 25.058.416 10 e 8.388.608 46.029.936 4 f 104.857.600 54.418.544 50 g 209.715.200 159.276.144100 h 8.388.608 368.991.344 4 gpart show output - sorted by sector offset: (#) (size)(offset) (GB) (offset*) (GiB*)(i) 1.048.57600,5 01 free b 8.318.0641.048.576 4 1.048.5764 2 7.303.1689.366.6403,5 9.366.6403 free a 8.388.608 16.669.808 4 16.669.8084 1 d 20.971.520 25.058.416 10 25.058.416 10 4 e 8.388.608 46.029.936 4 46.029.9364 5 f104.857.600 54.418.544 50 46.029.936 50 6 g209.715.200
More than 8 partitions
Hi I'm running 8.0-Release on an external usb hard drive. and have dual-boot with FreeBSD on da0s2 and Windows XP on da0s1. I made a setup via Sysinstall with 7 partitions: /dev/da0s2a on / (ufs, local) /dev/da0s2b (swap) /dev/da0s2d on /var (ufs, local, soft-updates) /dev/da0s2e on /tmp (ufs, local, soft-updates) /dev/da0s2f on /usr (ufs, local, soft-updates) /dev/da0s2h on /var/log (ufs, local, soft-updates) /dev/da0s2g on /home (ufs, local, soft-updates) I have about 660 GB left unused on da0s2 that I would like to use for backups. But I can't figure out how to create one more partition. If i create a file for bsdlabel like # sizeoffset fstype i: * 0 4.2BSD I get the following error message: line 2: partition name out of range a-h: i I have also tried with gpart: gpart add -s 500G -t freebsd -f x da0s2 I get something like gpart: index '9': No space left on device I thought that 8.0 should support more than 8 partitions. Maybe it does, but then I don't know how to do. Any ideas? Regards, Jon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Fwd: More than 8 partitions
-- Forwarded message -- From: Jon Theil Nielsen jonth...@gmail.com Date: 2010/4/30 Subject: Re: More than 8 partitions To: Alberto Mijares amijar...@gmail.com 2010/4/30 Alberto Mijares amijar...@gmail.com On Fri, Apr 30, 2010 at 1:14 PM, Jon Theil Nielsen jonth...@gmail.com wrote: Hi I'm running 8.0-Release on an external usb hard drive. and have dual-boot with FreeBSD on da0s2 and Windows XP on da0s1. I made a setup via Sysinstall with 7 partitions: /dev/da0s2a on / (ufs, local) /dev/da0s2b (swap) /dev/da0s2d on /var (ufs, local, soft-updates) /dev/da0s2e on /tmp (ufs, local, soft-updates) /dev/da0s2f on /usr (ufs, local, soft-updates) /dev/da0s2h on /var/log (ufs, local, soft-updates) /dev/da0s2g on /home (ufs, local, soft-updates) I have about 660 GB left unused on da0s2 that I would like to use for backups. But I can't figure out how to create one more partition. You should create a new slice (da0s3) and then create new partitions on it or use the whole slice (ad0s3c). Regards Alberto Mijares Thanks Alberto So it is *not* possible to have more than 8 partitions? Just a matter of interest, since I'm experimenting here. But nice to know. The next problem is that i made fdisk create the two slices covering all the space of the disk. Can I somehow - using FreeBSD tools - shrink the size of da0s2 without data loss? Regards, Jon - reposting this to the list... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Fwd: More than 8 partitions
2010/5/1 Da Rock freebsd-questi...@herveybayaustralia.com.au On Fri, 2010-04-30 at 19:44 +0200, Jon Theil Nielsen wrote: Hi I'm running 8.0-Release on an external usb hard drive. and have dual-boot with FreeBSD on da0s2 and Windows XP on da0s1. I made a setup via Sysinstall with 7 partitions: /dev/da0s2a on / (ufs, local) /dev/da0s2b (swap) /dev/da0s2d on /var (ufs, local, soft-updates) /dev/da0s2e on /tmp (ufs, local, soft-updates) /dev/da0s2f on /usr (ufs, local, soft-updates) /dev/da0s2h on /var/log (ufs, local, soft-updates) /dev/da0s2g on /home (ufs, local, soft-updates) I have about 660 GB left unused on da0s2 that I would like to use for backups. But I can't figure out how to create one more partition. If i create a file for bsdlabel like # sizeoffset fstype i: * 0 4.2BSD I get the following error message: line 2: partition name out of range a-h: i I have also tried with gpart: gpart add -s 500G -t freebsd -f x da0s2 I get something like gpart: index '9': No space left on device I thought that 8.0 should support more than 8 partitions. Maybe it does, but then I don't know how to do. Any ideas? Use vinum - thats what I needed to do. Mind I had around 15 partitions to work out so it is effective... Maybe I should consider that too. But this installation is quite experimental, and I just thought that it would be a simple task to make a few extra partitions, since that was what I read about when 8.0 was released. But I haven't found any documentation on the issue. I guess I either have to use some non-FreeBSD tool to change the size of my slices or backup the installation to another drive, rerun fdisk etc., and copy the system back. 'Regards, Jon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: More than 8 partitions
On Sat, May 1, 2010 at 1:58 AM, Jon Theil Nielsen jonth...@gmail.com wrote: So it is *not* possible to have more than 8 partitions? Just a matter of interest, since I'm experimenting here. But nice to know. Unlike OpenBSD's disklabel(8) which supports up to 15 partitions, bsdlabel(8) supports only 8 partitions (including the whole disk): http://www.openbsd.org/cgi-bin/man.cgi?query=disklabelsektion=8 http://www.freebsd.org/cgi/man.cgi?query=bsdlabelapropos=0sektion=0manpath=FreeBSD+8.0-RELEASEformat=html -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: More than 8 partitions
2010/5/1 C. P. Ghost cpgh...@cordula.ws On Sat, May 1, 2010 at 1:58 AM, Jon Theil Nielsen jonth...@gmail.com wrote: So it is *not* possible to have more than 8 partitions? Just a matter of interest, since I'm experimenting here. But nice to know. Unlike OpenBSD's disklabel(8) which supports up to 15 partitions, bsdlabel(8) supports only 8 partitions (including the whole disk): http://www.openbsd.org/cgi-bin/man.cgi?query=disklabelsektion=8 http://www.freebsd.org/cgi/man.cgi?query=bsdlabelapropos=0sektion=0manpath=FreeBSD+8.0-RELEASEformat=html -cpghost. -- Cordula's Web. http://www.cordula.ws/ I am very far from being an expert on these issues. And this link is certainly not documentation: http://ivoras.sharanet.org/freebsd/freebsd8.html But if I look into the source code of bsdlabel (/usr/src/sbin/bsdlabel/bsdlabel.c), I can see this: #define MAXPARTITIONS 26 which at least tells me that is has been the *intention* that it should be possible. Regards, Jon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: More than 8 partitions
On Sat, 1 May 2010 02:53:13 +0200, Jon Theil Nielsen jonth...@gmail.com wrote: But if I look into the source code of bsdlabel (/usr/src/sbin/bsdlabel/bsdlabel.c), I can see this: #define MAXPARTITIONS 26 which at least tells me that is has been the *intention* that it should be possible. Obviously, this refers to the possible letters a, b, c, ..., z as partition identifiers instead of numerical ones (e. g. ad0p7). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
