1. A molded respirator comprising a cup-shaped porous monocomponent monolayer matrix of continuous charged monocomponent polymeric fibers, the fibers being partially crystalline and partially amorphous oriented meltspun polymeric fibers of the same polymeric composition bonded to one another at at least some points of fiber intersection and the matrix having a King Stiffness greater than 1 N.
2. A molded respirator according to claim 1 wherein the fibers are autogenously bonded.
3. A molded respirator according to claim 1 wherein the matrix has a basis weight of about 80 to about 250 gsm.
4. A molded respirator according to claim 1 wherein the matrix has an Effective Fiber Diameter of about 5 to about 40 \u03bcm.
5. A molded respirator according to claim 1 wherein the matrix has a King Stiffness of at least 2 N.
6. A molded respirator according to claim 1 which exhibits less than 5% maximum penetration when exposed to a 0.075 \u03bcm sodium chloride aerosol flowing at 85 litersmin.
7. A molded respirator according to claim 1 which exhibits less than 1% maximum penetration when exposed to a 0.075 \u03bcm sodium chloride aerosol flowing at 85 litersmin.
8. A molded respirator according to claim 1 wherein the polymer is polypropylene.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A data storage device, comprising:
a head which reads and writes data on a rotating storage medium;
an actuator that positions the head on a desired track of the storage medium;
a control circuit which receives a write command and write data from a host, writes the write data on a specified track of the storage medium using the head, detects off track that the head is shifted a predetermined amount from the track, when the head is writing data on the track, and executes write retry of the write data on the track; and
a rewrite request table which stores a rewrite request,
wherein the control circuit, when the off track is detected, judges whether there is a possibility that data on an adjacent track is affected by off track of the head, stores a rewrite request for the adjacent track in the rewrite request table if it is judged that there is a possibility that the data on the adjacent track is affected, and executes the rewrite request stored in the rewrite request table at a timing which is different from the write retry.
2. The data storage device according to claim 1, wherein when the control circuit receives another write command, the control circuit executes the rewrite request stored in the rewrite request table before executing another write command.
3. The data storage device according to claim 1, wherein the control circuit judges whether a vibration which causes the off track is stopped, and executes the rewrite request stored in the rewrite request table when it is judged that the vibration is stopped.
4. The data storage device according to claim 2, wherein when the control circuit receives the other write command, the control circuit executes the rewrite request for a track adjacent to the track specified by the other write command stored in the rewrite request table before executing the other write command.
5. The data storage device according to claim 2, wherein when the other write command is received, the control circuit judges whether the rewrite request for a track adjacent to the track specified by the other write command exists in the rewrite request table, and executes the rewrite request for the adjacent track if the rewrite request for the adjacent track exists, and judges whether a vibration which causes the off track is stopped if the rewrite request for the adjacent track does not exist, and executes a rewrite request for a track other than the adjacent track stored in the rewrite request table if it is judged that the vibration is stopped.
6. The data storage device according to claim 1, wherein when another write command is received, the control circuit judges whether a rewrite area of the rewrite request in the rewrite request table is within a write range of the other write command, and resets the rewrite request stored in the rewrite request table when it is judged that the rewrite area of the rewrite request is within the write range of the other write command.
7. The data storage device according to claim 1, wherein the rewrite request table stores a plurality of rewrite requests each of which has at least a target track number and a shift amount of the head at the off track,
and if it is judged that there is a possibility that data on the adjacent track is affected, the control circuit compares the shift amount of the head of the rewrite request for the adjacent track and the shift amounts of the rewrite requests stored in the rewrite request table, and deletes the rewrite request of which the shift amount is the lowest from the rewrite request table.
8. The data storage device according to claim 1, wherein when it is judged that there is a possibility that the data on the adjacent track is affected, the control circuit judges whether the adjacent track is within a target range of the write command which generates the off track, and disables storing the rewrite request for the adjacent track in the rewrite request table when it is judged that the adjacent track is within the target range of the write command.
9. The data storage device according to claim 1, wherein the control circuit judges whether the write command is received, and executes the rewrite request stored in the rewrite request table if the write command is not received.
10. The data storage device according to claim 1, further comprising a cache memory that temporarily stores the write data,
wherein the control circuit judges whether the target data of the rewrite request of the rewrite request table exists in the cache memory, and executes the rewrite request by writing the target data in the cache memory on the adjacent track if the target data of the rewrite request exists in the cache memory.
11. The data storage device according to claim 10, wherein when it is judged that there is a possibility that the data on the adjacent track is affected, the control circuit judges whether the data on the adjacent track exists in the cache memory, and if judging that the data exists in the cache memory, the control circuit attaches an identifier existing in the cache memory to the rewrite request, stores the rewrite request in the rewrite request table, and executes the rewrite request having the identifier existing in the cache memory, which is stored in the rewrite request table, with priority at a timing which is different from the write retry.
12. An adjacent track rewrite processing method for a data storage device which positions a head for reading and writing data on a desired track of a rotating storage medium and reads and writes the data, comprising:
detecting off track that the head is shifted a predetermined amount from the track, when the head is writing data on the track;
judging whether there is a possibility that data on an adjacent track is affected by off track of the head when the off track is detected;
storing a rewrite request for the adjacent track in a rewrite request table if it is judged that there is a possibility that the data on the adjacent track is affected;
executing write retry of the write data on the track; and
executing the rewrite request stored in the rewrite request table at a timing which is different from the write retry.
13. The adjacent track rewrite processing method according to claim 12, wherein the executing the rewrite request comprises:
executing the rewrite request stored in the rewrite request table before executing the write command when another write command is received.
14. The adjacent track rewrite processing method according to claim 12, wherein executing the rewrite request further comprises:
judging whether a vibration which causes the off track is stopped; and
executing the rewrite request stored in the rewrite request table when it is judged that the vibration is stopped.
15. The adjacent track rewrite processing method according to claim 13, wherein executing the rewrite request further comprises:
executing the rewrite request for a track adjacent to the track specified by the write command stored in the rewrite request table before executing the write command when another write command is received.
16. The adjacent track rewrite processing method according to claim 13, wherein the executing the rewrite request further comprises:
judging whether the rewrite request for a track adjacent to the track specified by the write command exists in the rewrite request table when the other write command is received;
executing the rewrite request for the adjacent track if the rewrite request for the adjacent track exists;
judging whether a vibration which causes the off track is stopped if the rewrite request for the adjacent track does not exist; and
executing a rewrite request for a track other than the adjacent track stored in the rewrite request table if it is judged that the vibration is stopped.
17. The adjacent track rewrite processing method according to claim 12, wherein the executing the rewrite request further comprises:
judging whether a rewrite area of the rewrite request in the rewrite request table is within a write range of another write command when the other write command is received; and
resetting the rewrite request stored in the rewrite request table when it is judged that the rewrite area of the rewrite request is within the write range of the other write command.
18. The adjacent track rewrite processing method according to claim 12, wherein the storing comprises:
comparing the shift amount of the head of the rewrite request for the adjacent track and the shift amounts of the rewrite requests stored in the rewrite request table if it is judged that there is a possibility that data on the adjacent track is affected; and
deleting the rewrite request of which the shift amount is the lowest from the rewrite request table.
19. The adjacent track rewrite processing method according to claim 12, wherein the storing further comprises:
judging whether the adjacent track is within a target range of the write command which generates the off track if it is judged that there is a possibility that the data on the adjacent track is affected; and
disabling storing the rewrite request for the adjacent track in the rewrite request table when it is judged that the adjacent track is within the target range of the write command.
20. The adjacent track rewrite processing method according to claim 12, wherein the executing the rewrite request further comprises:
judging whether the write command is received, and a step of executing the rewrite request stored in the rewrite request table if the write command is not received.
21. The adjacent track rewrite processing method according to claim 12, wherein the executing the rewrite request further comprises:
judging whether the target data of the rewrite request of the rewrite request table exists in a cache memory which temporarily stores the write data; and
executing the rewrite request by writing the target data in the cache memory on the adjacent track if the target data of the rewrite request exists in the cache memory.
22. The adjacent track rewrite processing method according to claim 21,
wherein the storing further comprises;
judging whether the data on the adjacent track exists in the cache memory if it is judged that there is a possibility that the data on the adjacent track is affected; and
attaching an identifier existing in the cache memory to the rewrite request and storing the rewrite request in the rewrite request table if the data on the adjacent track exists in the cache memory, and
wherein the executing the rewrite request further comprises:
executing the rewrite request having the identifier existing in the cache memory, which is stored in the rewrite request table, with priority at a timing which is different from the write retry.