Page 1 of 1

corrupt config.xml file

Posted: 28 Nov 2013 18:38
by cruzmiester
below I included a portion of the config.xml file. the device that actually failed was device 6. I have replaced the faulty drive, but the array is still degraded. can anyone tell me what MIGHT happen if I manually delete the entry <device>/dev/5809131060538245674</device> and manually add the new drive that currently has id mfid7 in the disk list?

Thanks for the input
<zfs>
<vdevices>
<vdevice>
<uuid>3d727b58-ffd9-4154-b32d-5c6b0d37c84c</uuid>
<name>VD1</name>
<type>stripe</type>
<device>/dev/mfid8</device>
<device>/dev/mfid9</device>
<device>/dev/mfid10</device>
<desc/>
</vdevice>
<vdevice>
<uuid>22163432-1d87-43a5-8a72-6ef20e3850a6</uuid>
<name>disk1_raidz3_0</name>
<type>raidz3</type>
<device>/dev/mfid0</device>
<device>/dev/mfid1</device>
<device>/dev/mfid2</device>
<device>/dev/mfid3</device>
<device>/dev/5809131060538245674</device>
<device>/dev/mfid4</device>
<device>/dev/mfid5</device>
<device>/dev/mfid6</device>
<desc/>
</vdevice>
</vdevices>

Re: corrupt config.xml file

Posted: 03 Dec 2013 08:51
by shakky4711
Hi,

My first idea was that you simply made a mistake when you replaced the damaged drive, do not manipulate he config file!

Consider that the resilver (rebuild) process from a filled pool built with 3TB drives can take very long, did this process really finish?

Please inform us which steps you have taken to replace the drive.

Shakky