When e2fsck marks a new bad block (using either -c, -l or -L) and if also it is detected that the badblock is currently in use, does e2fsck make any attempt to preserve the data, by reading the value of the block and re-writing it elsewhere?
Of course, I appreciate that in the general case this is somewhat perverse since we can hardly have confidence in the data retrieved from a block which is in the process of being marked as bad! But it would be handy in some cases. For example, when marking a block bad in a "good" device of a raid1 array prior to adding back in a device where this block really has gone bad.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.