today I accidently deleted a folder of the last disk in the array.

 

Im in the process of rebuilding the folder tree as described here:

 

http://lime-technology.com/forum/index.php?topic=5087.msg47070#msg47070

 

when this finish and I remount/restart samba, will this rebuild process have affected the

parity in a bad way, or is the parity disk working with the system even while doing rebuild?

if not, will errors found during parity check correct the parity disk, or the named disk?

 

using unraid 4.5.4 (i think, can not access the web interface now)

 

thanks in advance for clearing up this.

 

today I accidently deleted a folder of the last disk in the array.

 

Im in the process of rebuilding the folder tree as described here:

 

http://lime-technology.com/forum/index.php?topic=5087.msg47070#msg47070

 

when this finish and I remount/restart samba, will this rebuild process have affected the

parity in a bad way, or is the parity disk working with the system even while doing rebuild?

if not, will errors found during parity check correct the parity disk, or the named disk?

 

using unraid 4.5.4 (i think, can not access the web interface now)

 

thanks in advance for clearing up this.

If you ran reiserfsck on the /dev/mdX device, then parity is corrected (being kept in sync) while the files are recovered.  You do not need to do anything more to get it in sync.

 

 

today I accidently deleted a folder of the last disk in the array.

 

Im in the process of rebuilding the folder tree as described here:

 

http://lime-technology.com/forum/index.php?topic=5087.msg47070#msg47070

 

when this finish and I remount/restart samba, will this rebuild process have affected the

parity in a bad way, or is the parity disk working with the system even while doing rebuild?

if not, will errors found during parity check correct the parity disk, or the named disk?

 

using unraid 4.5.4 (i think, can not access the web interface now)

 

thanks in advance for clearing up this.

If you ran reiserfsck on the /dev/mdX device, then parity is corrected (being kept in sync) while the files are recovered.  You do not need to do anything more to get it in sync.

 

is it safe to copy/move from lost and found to another location on the same disk (theres enough free space), or is the lost and found space free for the system to use.stupid question, but I dont want to screw up.

today I accidently deleted a folder of the last disk in the array.

 

Im in the process of rebuilding the folder tree as described here:

 

http://lime-technology.com/forum/index.php?topic=5087.msg47070#msg47070

 

when this finish and I remount/restart samba, will this rebuild process have affected the

parity in a bad way, or is the parity disk working with the system even while doing rebuild?

if not, will errors found during parity check correct the parity disk, or the named disk?

 

using unraid 4.5.4 (i think, can not access the web interface now)

 

thanks in advance for clearing up this.

If you ran reiserfsck on the /dev/mdX device, then parity is corrected (being kept in sync) while the files are recovered.  You do not need to do anything more to get it in sync.

 

is it safe to copy/move from lost and found to another location on the same disk (theres enough free space),

Yes.

or is the lost and found space free for the system to use.stupid question, but I dont want to screw up.

No, it is not specifically ear-marked for the system, but it is good practice to never fill a drive completely, as if a file needed to be recovered it could have some free blocks to recover to.