On Mon, Aug 4, 2008 at 6:50 PM, Edward Shishkin <edward.shishkin@xxxxxxxxx> wrote: > Dushan Tcholich wrote: >> On Mon, Aug 4, 2008 at 4:47 PM, Edward Shishkin >> <edward.shishkin@xxxxxxxxx> wrote: >> >>> Dushan Tcholich wrote: >>> >>>> Would it be possible if there would be a new version of fsck.reiser4 >>>> to fix those false positives about wrong size when checking >>>> cryptocompress partitions? >>>> >>>> >>> Yes, per-file warnings about wrong i_bytes should be suppressed. >>> Fsck just should report at the end of work in default mode, that N wrong >>> i_bytes were detected and suggest to fix it with --fix option. >>> Anyone care to try to make a patch? >>> >>> >> But what happens with systems with ccreg and fsck on boot? They would >> stop and wait for user interaction. >> > > Why? > Do you have any problems with boot? I don't have problems. I just thought that checking for these false positives lasted 10 minutes on my 6GB / so wouldn't this be a little too long if we don't put some status of some sorts? >> Or you meant just to print a message about it with recomended solution >> and continue. >> > > Everything should be the same except per-file warnings. > Maybe a better explanation would be better instead just: "600000 small errors found" :) >> I'd like to make a patch but dunno how :) >> >> >>>> There are some users that reported those and it's not comforting when >>>> your fs spews thousands of errors, even when someone tells you they're >>>> false. >>>> >>>> Oh and what about making cryptocompress default format on mkfs.reiser4 ? >>>> >>>> >>> mm.. not sure. First, fsck should be fixed to remove unprepped items. >>> >> Ofcourse. >> >> >>> Mr. Tao, do you still have partitions that make fsck segfault? >>> >>> Thanks, >>> Edward. >>> >>> >> Dushan >> >> > > -- To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
