From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anders Aagaard Subject: Re: Tested reiser4 and got some problems. Date: Thu, 07 Aug 2008 16:14:11 +0200 Message-ID: <489B0333.1080108@gmail.com> References: <489AF88C.2090605@gmail.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=mukw/Mbaimp59eXJYws++x0JUePXsQpHW4btoSLhr0A=; b=hAJZBFOUr3NpvqSl5JZDIf0C5mx2dqy+vv4uA2MCFqsCn0j0FdtBRDJ/j8A1/PUFq6 vE+PFeChO02Fy1uLAuAgg9CBnuZz+oSZcrbr2V6vfAibDEAIUU3MoEkpKR3m6xsCEn+o 064mN5L9ztQX6ttp7rFKXpxCEGFy9eOtDnrXQ= In-Reply-To: Sender: reiserfs-devel-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Dushan Tcholich Cc: reiserfs-devel@vger.kernel.org Dushan Tcholich wrote: > Hi > > Those are false positives when checking cryptocompress partitions, > because they are checked with checksumm so exact file size is not > required for check, and because that filesize is not being updated for > performance reasons. > This should be repaired in next version of reiser4.progs Ah very nice, it had me worried, I'll keep going until I find a real bug then ;) > > Here's some more info: > "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." > http://marc.info/?l=reiserfs-devel&m=121786117117164&w=2 > > I hope this helps > Dushan > On Thu, Aug 7, 2008 at 3:28 PM, Anders Aagaard wrote: >> Hi >> >> I just tested reiser4, and ran into some problems right away, with >> reiser4progs 1.0.6 and patches from >> http://www.kernel.org/pub/linux/kernel/people/edward/reiser4/reiser4-for-2.6/. >> Patched on top of gentoo-sources 2.6.25. >> >> After executing this on my test box: >> mkfs.reiser4 -o create=ccreg40,compress=lzo1 /dev/sdb2 >> mount -t reiser4 -o noatime /dev/sdb2 /mnt/sdb >> cd /mnt/sdb >> rsync -vax --exclude "/dev/" --exclude "/proc/" --exclude "/sys" --exclude >> "/mnt" --progress / . >> mkdir -p dev sys proc mnt mnt/cdrom >> mknod dev/console c 5 1 >> mknod dev/null c 1 3 >> cd .. >> umount /mnt/sdb >> fsck.reiser4 /dev/sdb2 >> >> fsck finds TONS of errors like this: >> FSCK: obj40_repair.c: 223: obj40_stat_unix_check: Node (718264), item (6), >> [67e01:2e524541444d45:67f16] (stat40): wrong bytes (65536), Should be (310). >> FSCK: obj40_repair.c: 223: obj40_stat_unix_check: Node (718264), item (8), >> [67e01:2e73657475702e:67f18] (stat40): wrong bytes (65536), Should be (152). >> FSCK: obj40_repair.c: 223: obj40_stat_unix_check: Node (718264), item (9), >> [67e01:2e73657475702e:67f19] (stat40): wrong bytes (65536), Should be (416). >> FSCK: obj40_repair.c: 223: obj40_stat_unix_check: Node (718264), item (7), >> [67e01:2e6d697373696e:67f17] (stat40): wrong bytes (65536), Should be >> (1635). >> FSCK: obj40_repair.c: 223: obj40_stat_unix_check: Node (718103), item (2), >> [67dcc:2e74627a32746f:67f0f] (stat40): wrong bytes (65536), Should be >> (2223). >> Found 360227 objects (some could be encountered more then once). >> Time interval: Thu Aug 7 14:01:13 2008 - Thu Aug 7 14:03:40 2008 >> >> After completing the fsck things seem fine, but it makes me slightly >> worried. There's no kernel oops'es or anything like that in dmesg, >> everything seemed perfectly fine until I did an fsck. Note that this is >> repeatable. >> >> Anders >> -- >> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> >