On 01/31/2017 10:38 PM, Andrei Borzenkov wrote:
01.02.2017 06:05, george from the tribe пишет:
But when I try this, there is a problem: # mke2fs -c -L root1bak ext4 -v /dev/sdb5 mke2fs 1.42.11 (09-Jul-2014) mke2fs: invalid blocks '/dev/sdb5' on device 'ext4'
What does 'invalid blocks' mean? And how do I fix this?
You are attempting to create filesystem with size "/dev/sdb5" on device "ext4". Is it what you really intend to do?
Well, yes there is that LOL! If you really really really do want to deal with bad blocks, the ... FIRST run the 'badblocks, tool on the physical device or partition. See BADBLOCKS(8) In particular note the caveat about block size. Depending on the parameters and the size of the drive/partition this may take some time. I once had a new gigadisk that was giving problems and ran this to give evidence to the vendor for returning it. That ran all day and all night. NEXT use the output of that with the 'e2fsck' to fix the file system. Or, if you are doing a 'mkfs.ext4', use the "-l" option to make use of the list generated by 'badblocks'. Yes, 'mkfs.ext4' does have the "-c" parameter to do its own checking. I don't think it is so configurable or as flexible as 'badblocks'. However using it does get around any mismatch issue about blocksize, so the manual page recommends that. YMMV -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org