Restrictions and guidelines, Configuration procedure, Displaying and maintaining the nand flash memory – H3C Technologies H3C SecBlade LB Cards User Manual
Page 92: Displaying and repairing bad blocks
83
Product Feature
compatible
LB module
Yes
Restrictions and guidelines
It is normal that the configured partition size and the actual partition size have an error less than 5% of
the total memory.
Before partitioning a CF card, back up the files in the storage medium. The partition operation clears all
data in the medium.
After partitioning a CF card:
•
Reconfigure paths of application files to include the correct partition information.
•
If the device starts up from the CF card, put the startup system software image file and the
configuration file in the first partition of the CF card.
•
To guarantee the startup system software image and configuration files sufficient storage space, set
the path for log files to a partition other than the first partition. By default, the system automatically
saves log files to the second partition. If the path does not exist, use the info-center logfile
switch-directory command to change the path to avoid log loss. For more information about this
command, see System Maintenance Command Reference.
•
To avoid file system corruption, unmount all the partitions before removing a storage medium.
Configuration procedure
Perform this task in user view.
Task Command
Remarks
Partition a CF card.
fdisk medium-name
[ partition-number ]
By default, only one partition cfa0:/
is available on a CF card.
Displaying and maintaining the NAND Flash memory
The physical space of the NAND Flash memory is divided into multiple blocks, each of which is
subdivided into multiple pages. The NAND Flash memory is erased on a block basis and read on a
page basis; the memory spaces are allocated on a page basis.
The following matrix shows the feature and LB product compatibility:
Product Feature
compatible
L1000-A
Yes
LB module
No
Displaying and repairing bad blocks
Bad block ratio varies with products of different vendors. Bad blocks cannot be used to store data, and
the system has to skip the bad blocks when it allocates storage spaces to files. You can get the locations
of bad blocks and repair them at the CLI.
To display and repair bad blocks: