Hi:

I use a script to generate images for the compact flash disks I use in
my Soekris net4801 devices.

I recently switched to 1.0 GB SanDisk CF. I can generate images no
problem, but at boot time, we see this warning:

> Automatic boot in progress: starting file system checks.
> /dev/rwd0a: file system is clean; not checking
> /dev/rwd0d: file system is clean; not checking
> Warning: inode blocks/cyl group (16) >= data blocks (12) in last
>     cylinder group. This implies 384 sector(s) cannot be allocated.
> Warning: inode blocks/cyl group (16) >= data blocks (12) in last
>     cylinder group. This implies 384 sector(s) cannot be allocated.

I don't know what this means.

Here is output from disklabel for the device in question:

> Disk: wd0       geometry: 993/32/63 [2001888 Sectors]
> Offset: 0       Signature: 0xAA55
>          Starting       Ending       LBA Info:
>  #: id    C   H  S -    C   H  S [       start:      size   ]
> ------------------------------------------------------------------------
>  0: 00    0   0  0 -    0   0  0 [           0:           0 ] unused
>  1: 00    0   0  0 -    0   0  0 [           0:           0 ] unused
>  2: 00    0   0  0 -    0   0  0 [           0:           0 ] unused
> *3: A6    0   1  1 -  992  31 63 [          63:     2001825 ] OpenBSD
> # disklabel wd0
> # Inside MBR partition 3: type A6 start 63 size 2001825
> # /dev/rwd0c:
> type: ESDI
> disk:
> label: sd1024
> flags:
> bytes/sector: 512
> sectors/track: 63
> tracks/cylinder: 32
> sectors/cylinder: 2016
> cylinders: 993
> total sectors: 2001888
> rpm: 3600
> interleave: 1
> trackskew: 0
> cylinderskew: 0
> headswitch: 0           # microseconds
> track-to-track seek: 0  # microseconds
> drivedata: 0
> 
> 5 partitions:
> #             size        offset  fstype [fsize bsize  cpg]
>   a:        100737            63  4.2BSD   1024  8192   49 # Cyl     0*-    49
>   b:             1        100800    swap                   # Cyl    50 -    
> 50*
>   c:       2001888             0  unused      0     0      # Cyl     0 -   992
>   d:        510048        102816  4.2BSD   1024  8192   86 # Cyl    51 -   303
>   e:       1389024        612864  4.2BSD   1024  8192   86 # Cyl   304 -   992

To my eye, everything looks kosher. The device seems to work just fine,
but before I deploy this I would like to know exactly what is going on here.

Any ideas?

Thanks,

-Stephen-

Reply via email to