devfs promlem: creating new partition in empty slice

Eugene Grosbein eugen at kuzbass.ru
Sat Mar 10 16:19:15 UTC 2007


Hi!

There is FreeBSD 6.2-STABLE (updated yesterday) having single
SATA drive. The drive has two equal-sized slices ad4s1 and ad4s2,
both marked with sysid 165 (FreeBSD).

The system occupies ad4s1 (partitions from a to h),
and ad4s2 is empty. This scheme was created at installation time
with sysinstall started by system boot CD (official disk1).

Now, when the system is up and running, I need to create partitions
within slice ad4s2. Questions are:

1. Do I really need 'sysctl kern.geom.debugflags=16'
if I do not want to touch MBR or living slice at all, and why, if I do?

2. How should I create new partitions within ad4s2? I've tried
to use sysinstall, it fills bsdlabel right but fails to newfs/mount
new partitions because device nodes do not exist. So now I have this:

# bsdlabel ad4s2                                                      
# /dev/ad4s2:
8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  a:   524288  2097152    4.2BSD        0     0     0 
  b:  2097152        0      swap                    
  c: 78702435        0    unused        0     0         # "raw" part, don't edit
  d:   524288  2621440    4.2BSD        0     0     0 
  e:  4194304  3145728    4.2BSD        0     0     0 
  f: 20971520  7340032    4.2BSD        0     0     0 
  g: 20971520 28311552    4.2BSD        0     0     0 
  h: 29419363 49283072    4.2BSD        0     0     0 

# ls -l /dev/ad4s2*                                                   
crw-r-----  1 root  operator    0,  75 10 мар 14:53 /dev/ad4s2
crw-r-----  1 root  operator    0,  84 10 мар 14:53 /dev/ad4s2c

What should I do now to get needed device nodes? The server is remote one,
it runs in production and I'd prefer to not reboot it.

Eugene Grosbein


More information about the freebsd-stable mailing list