tellus:~# hdparm -tT /dev/onetb/video

/dev/onetb/video:
Timing cached reads: 1696 MB in 2.00 seconds = 846.01 MB/sec
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device
Timing buffered disk reads: 246 MB in 3.02 seconds = 81.55 MB/sec
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device

so.. 85MB/sec read .. not bad. ( sinlge disk ca. 60MB )

make a existing lvm device bigger...

ugh - we run out of space !

# df
/dev/mapper/onetb-vmware 20158332 19089688 44644 100% /mnt/onetb/vmware

# lvextend -L+20G /dev/onetb/vmware
  Extending logical volume vmware to 39,53 GB
  Logical volume vmware successfully resized

so we have now "more space on the disk"

next, we need to let the ext3 know about this...

# umount /mnt/onetb/vmware
( e2fsck on mouted devices is bad... - but it will let you know ;-)

#:/# e2fsck -f /dev/onetb/vmware
e2fsck 1.37 (21-Mar-2005)
Durchgang 1: Prüfe Inodes, Blocks, und Größen
Durchgang 2: Prüfe Verzeichnis Struktur
Durchgang 3: Prüfe Verzeichnis Verknüpfungen
Durchgang 4: Überprüfe die Referenzzähler
Durchgang 5: Überprüfe Gruppe Zusammenfassung

/dev/onetb/vmware: ***** DATEISYSTEM WURDE VERÄNDERT *****
/dev/onetb/vmware: 71/2562240 Dateien (19.7% nicht zusammenhängend), 4852839/5120000 Blöcke

now do the resize...

#:/ resize2fs /dev/onetb/vmware
resize2fs 1.37 (21-Mar-2005)
Resizing the filesystem on /dev/onetb/vmware to 10362880 (4k) blocks.
Das Dateisystem auf /dev/onetb/vmware ist nun 10362880 Blöcke groß.

hehe, problem solved :-)
# df
/dev/mapper/onetb-vmware 40802112 19089688 19639848 50% /mnt/onetb/vmware

a 1TB disk is great - but it's also to big.
Not in size, but to handle in a good way.

e.g.: you store your /home, some photos, your mp3's there... some things you want to share, some not :)
also, it's a question of importance: your /home you wana keep forever, the scratch - directory you might loose wihtout to big impact...

here's a howto... (nice !)
http://www.void.gr/kargig/blog/2004/09/24/raid5-lvm2-recovery-resize-howto/

so.. create a PV
debian:/etc/lvm# pvcreate /dev/md0
  Physical volume "/dev/md0" successfully created

create a VG
debian:/etc/lvm# vgcreate onetb /dev/md0
  Incorrect metadata area header checksum
  Incorrect metadata area header checksum
  Incorrect metadata area header checksum
  Volume group "onetb" successfully created

and create a LV.
debian:/etc/lvm# lvcreate -L100000 -nvideo onetb
  Incorrect metadata area header checksum
  Logical volume "video" created
debian:/etc/lvm# mke2fs -j /dev/onetb/video
mke2fs 1.37 (21-Mar-2005)
Dateisystem-Label=
OS-Typ: Linux
Blockgröße=4096 (log=2)
Fragmentgröße=4096 (log=2)
12812288 Inodes, 25600000 Blöcke
1280000 Blöcke (5.00%) reserviert für den Superuser
erster Datenblock=0
782 Blockgruppen
32768 Blöcke pro Gruppe, 32768 Fragmente pro Gruppe
16384 Inodes pro Gruppe
Superblock-Sicherungskopien gespeichert in den Blöcken:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872

Schreibe Inode-Tabellen: erledigt
Erstelle Journal (8192 Blöcke): erledigt
Schreibe Superblöcke und Dateisystem-Accountinginformationen: erledigt

Das Dateisystem wird automatisch alle 24 Mounts bzw. alle 180 Tage überprüft,

now, you have a 100Gig FS ( a ext3 ) named "video". easy to mount

debian:/mnt/onetb# mount /dev/onetb/video /mnt/onetb/video/

so, this one I like to export. ( SMB or NFS.. ) but  read-only.

how I created the Raid-5...

( images are here: http://www.la-evento.com/urlaub/1tb )

debian:/etc/mdadm# apt-get install mdadm

debian:/etc/mdadm# vi mdadm.conf

debian:/etc/mdadm# more mdadm.conf
DEVICE /dev/sd[abcd]1
ARRAY /dev/md0 devices=/dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1

debian:/etc/mdadm# more /proc/mdstat
Personalities :
unused devices:

debian:/etc/mdadm# mdadm -C /dev/md0 --level=raid5 --raid-devices=4 /dev/sda1 /d ev/sdb1 /dev/sdc1 /dev/sdd1
mdadm: array /dev/md0 started.

debian:/etc/mdadm# more /proc/mdstat Personalities : [raid5] [raid4]
md0 : active raid5 sdd1[4] sdc1[2] sdb1[1] sda1[0]
937705728 blocks level 5, 64k chunk, algorithm 2 [4/3] [UUU_]
[>....................] recovery = 0.1% (359680/312568576) finish=101.2m
in speed=51382K/sec




just for testing ( fun ? ) - one big fs...

debian:/etc/mdadm# mke2fs -j /dev/md0
mke2fs 1.37 (21-Mar-2005)
Dateisystem-Label=
OS-Typ: Linux
Blockgröße=4096 (log=2)
Fragmentgröße=4096 (log=2)
117227520 Inodes, 234426432 Blöcke
11721321 Blöcke (5.00%) reserviert für den Superuser
erster Datenblock=0
7155 Blockgruppen
32768 Blöcke pro Gruppe, 32768 Fragmente pro Gruppe
16384 Inodes pro Gruppe
Superblock-Sicherungskopien gespeichert in den Blöcken:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
        102400000, 214990848

unused devices:

-------------------------
and whoooow... even the single disk is fast..
debian:/etc/mdadm# hdparm -tT /dev/sda1

/dev/sda1:
 Timing cached reads:   1056 MB in  2.00 seconds = 528.16 MB/sec
 Timing buffered disk reads:  188 MB in  3.00 seconds =  62.64 MB/sec

debian:/etc/mdadm# mke2fs -j /dev/md0
mke2fs 1.37 (21-Mar-2005)
Dateisystem-Label=
OS-Typ: Linux
Blockgröße=4096 (log=2)
Fragmentgröße=4096 (log=2)
117227520 Inodes, 234426432 Blöcke
11721321 Blöcke (5.00%) reserviert für den Superuser
erster Datenblock=0
7155 Blockgruppen
32768 Blöcke pro Gruppe, 32768 Fragmente pro Gruppe
16384 Inodes pro Gruppe
Superblock-Sicherungskopien gespeichert in den Blöcken:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
        102400000, 214990848

Schreibe Inode-Tabellen: erledigt
Erstelle Journal (8192 Blöcke): erledigt
Schreibe Superblöcke und Dateisystem-Accountinginformationen: erledigt

Das Dateisystem wird automatisch alle 37 Mounts bzw. alle 180 Tage überprüft,
je nachdem, was zuerst eintritt. Veränderbar mit tune2fs -c oder -t .

debian:/mnt# mkdir md0

debian:/mnt# mount /dev/md0 /mnt/md0/

debian:/mnt# df
Dateisystem          1K-Blöcke   Benutzt Verfügbar Ben% Eingehängt auf
/dev/hda1              8651248   1707000   6504788  21% /
tmpfs                   225644         0    225644   0% /dev/shm
/dev/md0             922990716     32828 876072604   1% /mnt/md0

*whoooa* ! 922 GB space :-)

i build a 1 TB raid5 linux-based storage with linux-software-raid.

some infos & the plan
=====================

here a "pro" to linux-software-raid.
http://linux.yyz.us/why-software-raid.html

hardware I will use.
* the of-the-shelf computer
* * a celeron 3ghz
* * 512mb ram
* * a 10gb IDE hard disk for the os.
* * 100mb built-in lan. (bad, because this will limit to 10mb/s max. ... maybe a 1gb card for future ? )

* the storage
* 4 * SATA WD 320gb disks (16mb cache, raid edition) (ok, it's a 3 * 320gb = 0.96 TB :)

software
* linux debian sarge with a 2.6.16 patched kernel to accept the via8251 SATA
* linux-software-raid 5
* LVM ( tbd. )
* ext3 FS. ( not the fastest, but bullet-prove and very well tested. (heard horrible stories about reiser & co.) )
* NFS, SMB/CIFS

who needs a TB ?
* i have my data currently on several disk ( about 5 - 7 )
* single disks are bad. they will die.
* using for storing photos, videos ( think on a digital video recorder )
* when I started 15 years ago, i had a 40mb disk, 4 mb ram. ...
* I'm a programmer - "deleting" is not my favor.

realisation phase
=================
* got a 10 gig ide drive for the OS.
* got my 5 disk ( 320 gig, wd. raid edition. ) ( one of them is a spare-disk ) pictures of the disks
* eeek. my 512mb ram is dead. this will delay everything. ... and fixed again. RAM seems to be more expensive these days... ;-/
*