From owner-freebsd-questions Sat Feb 19 2:10: 7 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.ariadne-t.gr (mail.ariadne-t.gr [143.233.30.3]) by hub.freebsd.org (Postfix) with SMTP id 8327C37BB0F for ; Sat, 19 Feb 2000 02:09:56 -0800 (PST) (envelope-from mdraco@math.uoa.gr) Received: (qmail 27066 invoked from network); 19 Feb 2000 10:10:07 -0000 Received: from ppp6c1.dialup.ariadne-t.gr (HELO comet.db.org) (143.233.100.6) by mail.ariadne-t.gr with SMTP; 19 Feb 2000 10:10:07 -0000 Received: from localhost (mike@localhost) by comet.db.org (8.9.3/8.9.3) with ESMTP id MAA00383; Sat, 19 Feb 2000 12:13:22 +0200 (EET) (envelope-from mike@comet.db.org) Date: Sat, 19 Feb 2000 12:13:21 +0200 (EET) From: Mike Dracopoulos To: freebsd-fs@FreeBSD.ORG Cc: freebsd-questions@FreeBSD.ORG Subject: duplicate blocks in shared ext2 partition Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am running both FreeBSD and Linux sharing an ext2 /home (on a dedicated disk). Occasionally (say once every month or two), FreeBSD complains on bootup about /home and asks to run fsck on it. Here is a record of what happened last time: 1) I was running FreeBSD day after day for quite some time 2) I rebooted to Linux to check something, no problems so far. 3) Back to FreeBSD, I get the complaint about /home 4) Reboot to Linux, and the boot-time fsck gives me: Inode 51214, i_block is 4, should be 2... Duplicate or bad blocks in use Duplicate blocks found, invoking duplicate block passes /dev/hdc1: Duplicate/bad block(s) in inode 100354 ... /dev/hdc1: Duplicate/bad block(s) in inode 163924 ... ... There are 2 inodes containing duplicate/bad blocks /dev/hdc1: File "SOME_FILE_A" (inode #163924, modified ... Feb 18...) has 1 duplicate block, shared with 2 files /dev/hdc1: /dev/hdc1: "SOME_FILE_B" (inode #100354, modified ... Feb 15 ...) /dev/hdc1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY 5) Running fsck and accepting everything, solves the problem for the time being. Please note, that FILE_A and B are unrelated context-wise and in terms of directory structure wise and modification/creation times, and not always the same 2 that trigger this problem. Thanks in advance for your help Mike Dracopoulos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message