Comment 2 for bug 447816

Ok, but where does the issue belong?
The problem is the behaviour of fsck, which is part of e2fsprogs, which is why I filed it against e2fsprogs.
I realize there is nothing wrong in the e2fsprogs package, but there is something wrong with the communication between the user and e2fsprogs, which needs some kind of solution before karmic is released.
Do you have a better idea of where this bug belongs?