touch-packages team mailing list archive

[Theodore Ts'o <tytso@xxxxxxx>]

The badblocks program really isn't designed to catch maliciously
designed "fake" flash FTL's.  The "bit dropping pages" aren't
necessarily constant, which means there might not be a set of block
numbers that you can _put_ in the bad block inode.   The bad block inode
is a bad idea in these modern days anyway.   It made sense back in the
days of IDE disks, or its predecessors, which didn't do the bad block
remapping in the drive firmware.   These days, it just causes confusion
and data loss by users who think it's a good idea.

I'm of half a mind of deprecating and disabling badblocks and e2fsck -cc
in the next major release of e2fsprogs, since more and more users are
using it to their detriment, and while I can't legislate away stupid
user tricks, I can remove tools that invite stupid user tricks....

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/796717

Title:
  e2fsck not fixing some fs errors

Status in e2fsprogs package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: e2fsprogs

  I've got a software RAID10 in Ubuntu 10.04 that started giving me fs
  errors Saturday evening. After running e2fsck multiple times and
  fixing many errors, it seems there are three left that it is not
  fixing even after multiple runs.

  Description:    Ubuntu 10.04.2 LTS
  Release:        10.04

  e2fsprogs:
    Installed: 1.41.11-1ubuntu2.1
    Candidate: 1.41.11-1ubuntu2.1
    Version table:
   *** 1.41.11-1ubuntu2.1 0
          500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
          100 /var/lib/dpkg/status
       1.41.11-1ubuntu2 0
          500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/796717/+subscriptions