Discussion:
something wrong with softraid
(too old to reply)
kasak
2017-12-20 19:33:40 UTC
Permalink
please help, I just noticed this strange thing:

$ df -h
Filesystem     Size    Used   Avail Capacity  Mounted on
/dev/sd0a     1005M   1004M  -49.6M   105%    /
/dev/sd0k     26.0G    2.3G   22.4G     9%    /home
/dev/sd0d      3.9G    138K    3.7G     0%    /tmp
/dev/sd0f      2.0G    795M    1.1G    42%    /usr
/dev/sd0g     1005M    215M    740M    23%    /usr/X11R6
/dev/sd0h      6.8G    799M    5.7G    12%    /usr/local
/dev/sd0j      2.0G    2.0K    1.9G     0%    /usr/obj
/dev/sd0i      1.9G    2.0K    1.8G     0%    /usr/src
/dev/sd0e      6.3G    1.1G    4.9G    18%    /var
/dev/sd4a      1.8T    1.3T    375G    79%    /bigdisk

look at /dev/sd0a

i've done some inspection and found this:

$ ls -alh /dev/rsd4
-rw-r--r--  1 root  wheel   913M Nov 14 20:58 /dev/rsd4

sd4 is my raid, bioctl shows nothing strange:

$ doas bioctl sd4
Volume      Status               Size Device
softraid0 0 Online      2000396018176 sd4     RAID1
          0 Online      2000396018176 0:0.0   noencl <sd1a>
          1 Online      2000396018176 0:1.0   noencl <sd2a>

How this can be?

just in case here is my fstab:

$ cat /etc/fstab
98afe66b05b9c528.b none swap sw
98afe66b05b9c528.a / ffs rw 1 1
98afe66b05b9c528.k /home ffs rw,nodev,nosuid 1 2
98afe66b05b9c528.d /tmp ffs rw,nodev,nosuid 1 2
98afe66b05b9c528.f /usr ffs rw,nodev 1 2
98afe66b05b9c528.g /usr/X11R6 ffs rw,nodev 1 2
98afe66b05b9c528.h /usr/local ffs rw,nodev,wxallowed 1 2
98afe66b05b9c528.j /usr/obj ffs rw,nodev,nosuid 1 2
98afe66b05b9c528.i /usr/src ffs rw,nodev,nosuid 1 2
98afe66b05b9c528.e /var ffs rw,nodev,nosuid 1 2
e642bdec5dc6a630.a /bigdisk ffs rw,nodev,nosuid,softdep 1 2
52dba8d6fdf64014.a /altroot ffs xx 0 0
Todd C. Miller
2017-12-20 21:13:32 UTC
Permalink
There should be no /dev/rsd4, the correct device nodes are /dev/rsd4a
through /dev/rsd4p. As you've shown, the /dev/rsd4 file you have
is not a device node anyway, it is a regular file.

You might want to take a look at its contents to try to understand
what created it but it should be safe to just remove it. Most
likely the file was created via a typo at some point.

- todd

Loading...