Large filesystem woes

[Giorgos Keramidas]

On 2005-07-28 16:04, dpk <dpk at dpk.net> wrote:
> # df -k
> Filesystem  1K-blocks    Used    Avail Capacity  Mounted on
> /dev/da0s1a  35082074 1147642 31127868     4%    /
> devfs               1       1        0   100%    /dev
> procfs              4       4        0   100%    /proc
> # fdisk -u
> fdisk: cannot open disk /dev/da0: No such file or directory
> # ls -ald /dev/da0*
> crw-r-----  1 root  operator    4,  12 Jul 28 15:56 /dev/da0
> crw-r-----  1 root  operator    4,  13 Jul 28 15:56 /dev/da0s1
> crw-r-----  1 root  operator    4,  18 Jul 28 08:56 /dev/da0s1a
> crw-r-----  1 root  operator    4,  19 Jul 28 15:56 /dev/da0s1b
> crw-r-----  1 root  operator    4,  20 Jul 28 15:56 /dev/da0s1c
>
> truss indicates that fdisk may be getting the error from somewhere else:
>
> stat("/dev/da0",0xbfbfeb30)                      = 0 (0x0)
> open("/dev/da0",0x2,00)                          ERR#1 'Operation not permitted'
> open("/dev/da0",0x0,027757765630)                = 6 (0x6)
> open("/dev/da0s1",0x2,01001210100)               ERR#1 'Operation not permitted'
> open("/dev/da0s2",0x2,01001210100)               ERR#2 'No such file or directory'
> open("/dev/da0s3",0x2,01001210100)               ERR#2 'No such file or directory'
> open("/dev/da0s4",0x2,01001210100)               ERR#2 'No such file or directory'
>
> Because it is using devfs, I'm not able to create these missing slices in
> /dev. Most unfortunately, it appears it uses devfs in single user mode as
> well, so I can't test the theory.

Hmmm, in multiuser mode, your root filesystem is mounted as read-write
and it resides in da0, so GEOM will forbid opening the disk device in
read-write mode for editing the partition table.

In single user mode, devfs is still used, but your root filesystem
should be mounted read-only (unless you manually mount it as
read-write), so fdisk -u should work.