07.06.2014 Views

2 - Raspberry PI Community Projects

2 - Raspberry PI Community Projects

2 - Raspberry PI Community Projects

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

# mdadm --detail /dev/md1<br />

/dev/md1:<br />

Version : 1.2<br />

Creation Time : Thu Sep 30 15:39:13 2010<br />

Raid Level : raid1<br />

Array Size : 4194240 (4.00 GiB 4.29 GB)<br />

Used Dev Size : 4194240 (4.00 GiB 4.29 GB)<br />

Raid Devices : 2<br />

Total Devices : 2<br />

Persistence : Superblock is persistent<br />

Update Time : Thu Sep 30 15:39:26 2010<br />

State : active, resyncing<br />

Active Devices : 2<br />

Working Devices : 2<br />

Failed Devices : 0<br />

Spare Devices : 0<br />

Rebuild Status : 10% complete<br />

Name : squeeze:1 (local to host squeeze)<br />

UUID : 20a8419b:41612750:b9171cfe:00d9a432<br />

Events : 27<br />

Number Major Minor RaidDevice State<br />

0 8 98 0 active sync /dev/sdg2<br />

1 8 112 1 active sync /dev/sdh<br />

# mdadm --detail /dev/md1<br />

/dev/md1:<br />

[...]<br />

State : active<br />

[...]<br />

TIP<br />

RAID, disks and partitions<br />

As illustrated by our example, RAID devices can be constructed out of disk<br />

partitions, and do not require full disks.<br />

A few remarks are in order. First, mdadm notices that the physical elements have different sizes;<br />

since this implies that some space will be lost on the bigger element, a confirmation is required.<br />

More importantly, note the state of the mirror. The normal state of a RAID mirror is that both<br />

disks have exactly the same contents. However, nothing guarantees this is the case when the<br />

volume is first created. The RAID subsystem will therefore provide that guarantee itself, and<br />

304 The Debian Administrator's Handbook

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!