Subject: Raid out of space?
To: netbsd-users@netbsd.org <netbsd-users@netbsd.org>
From: Jorgen Lundman <lundman@lundman.net>
List: netbsd-users
Date: 02/06/2001 10:02:30
I'm no raid expert, so perhaps someone can help. :)

raid0 situation, with 2 drives. Roughly 80gigs free and it says out of
space:

sycamore# df
Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
/dev/raid0c 116402501 31915120 78667255    28%    /incoming

and inodes as:
Filesystem  1K-blocks     Used    Avail Capacity iused   ifree  %iused 
Mounted on
/dev/raid0c 116402501 31915120 78667255    28%    2283 29243155     0%  
/incoming

Now if I ssue something like:

sycamore# cp /netbsd /incoming
/incoming: write failed, file system is full
cp: /incoming/netbsd: No space left on device

If I clear 2 megs space, I get 2 megs to play with before it is full.




Raid0.conf

# Lundy's 3rd RAID control attempt
# Second argument is number of drives, ie, 2
START array
1 2 0

START disks
/dev/wd1e
/dev/wd3e

START layout
# sectPerSU SUsPerParityUnit SUsPerReconUnit RAID_level
64   1    1    0


START queue
fifo 100


Raid status

sycamore# raidctl -s raid0
Components:
           /dev/wd1e: optimal
           /dev/wd3e: optimal
No spares.
Component label for /dev/wd1e:
   Row: 0 Column: 0 Num Rows: 1 Num Columns: 2
   Version: 2 Serial Number: 31337 Mod Counter: 1681242487
   Clean: No Status: 0
   sectPerSU: 64 SUsPerPU: 1 SUsPerRU: 1
   RAID Level: 0  blocksize: 512 numBlocks: 120101760
   Autoconfig: No
   Root partition: No
   Last configured as: raid0
Component label for /dev/wd3e:
   Row: 0 Column: 1 Num Rows: 1 Num Columns: 2
   Version: 2 Serial Number: 31337 Mod Counter: 1681242487
   Clean: No Status: 0
   sectPerSU: 64 SUsPerPU: 1 SUsPerRU: 1
   RAID Level: 0  blocksize: 512 numBlocks: 120101760
   Autoconfig: No
   Root partition: No
   Last configured as: raid0
Parity status: clean
Reconstruction is 100% complete.
Parity Re-write is 100% complete.
Copyback is 100% complete.


Raid disklabel:

sycamore# disklabel raid0
# /dev/rraid0d:
type: RAID
disk: raid
label: default label
flags:
bytes/sector: 512
sectors/track: 128
tracks/cylinder: 10
sectors/cylinder: 1280
cylinders: 187659
total sectors: 240203520
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0           # microseconds
track-to-track seek: 0  # microseconds
drivedata: 0 

4 partitions:
#        size   offset     fstype   [fsize bsize   cpg]
  c: 240203520        0     4.2BSD     1024  8192    82   # (Cyl.    0 -
187658)
  d: 240203520        0     4.2BSD     1024  8192    69   # (Cyl.    0 -
187658)


wd1's disklabel:

# /dev/rwd1d:
type: ESDI
disk: IBM-DTLA-307060 
label: fictitious
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 16383
total sectors: 120103200
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0           # microseconds
track-to-track seek: 0  # microseconds
drivedata: 0 

8 partitions:
#        size   offset     fstype   [fsize bsize   cpg]
  d: 120103200        0     unused        0     0         # (Cyl.    0 -
119149)
  e: 120101877       63       RAID                        # (Cyl.    0*-
119148*)


wd3's disklabel:

sycamore# disklabel wd3
# /dev/rwd3d:
type: ESDI
disk: IBM-DTLA-307060 
label: fictitious
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 16383
total sectors: 120103200
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]
  d: 120103200        0     unused        0     0         # (Cyl.    0 -
119149)
  e: 120103200        0     4.2BSD     1024  8192    16   # (Cyl.    0 -
119149)



I notice an inconsistency here, is this the cause of the problem? What
needs to be done to correct it? Will we lose raid?


Also found that I can create a file, like:

sycamore# dd if=/dev/zero of=testing bs=1024

/incoming: write failed, file system is full
dd: testing: No space left on device
42825+0 records in
42824+0 records out
43851776 bytes transferred in 45 secs (974483 bytes/sec)

-rw-r--r--   1 root  wheel  43851776 Feb  6 11:54 testing


Leaving the file there, I can then go create a second file:

sycamore# dd if=/dev/zero of=testing2 bs=1024

/incoming: write failed, file system is full
dd: testing2: No space left on device
42769+0 records in
42768+0 records out
43794432 bytes transferred in 38 secs (1152485 bytes/sec)

-rw-r--r--   1 root  wheel  43851776 Feb  6 11:54 testing
-rw-r--r--   1 root  wheel  43794432 Feb  6 11:55 testing2

and slowly fill up the system?



Any reply would be appreciated!

Lund

-- 
Jorgen "Lord" Lundman <lundman@lundman.net>
Technology Manager, Unix Administrator
Phone: +44 (020)8659-1860  Mobile: (07958)642-918
Pager: 07958642918@one2one.net
"Rare is the person who can weigh the faults of others 
 without putting his thumb on the scales": Byron J. Langenfeld