From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Stephen Elliott" Subject: RE: 2nd Attempt - FSCK Errors Date: Wed, 8 May 2013 16:20:28 +0100 Message-ID: <001501ce4bff$93070ea0$b9152be0$@ntlworld.com> Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE To: Return-path: Received: from mail-wi0-f170.google.com ([209.85.212.170]:48081 "EHLO mail-wi0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756359Ab3EHPU2 convert rfc822-to-8bit (ORCPT ); Wed, 8 May 2013 11:20:28 -0400 Received: by mail-wi0-f170.google.com with SMTP id hq12so5411801wib.5 for ; Wed, 08 May 2013 08:20:27 -0700 (PDT) Received: from STEVEHP (know-mailgateway-3.server.virginmedia.net. [62.254.26.105]) by mx.google.com with ESMTPSA id e8sm9886317wic.5.2013.05.08.08.20.25 for (version=TLSv1.1 cipher=RC4-SHA bits=128/128); Wed, 08 May 2013 08:20:26 -0700 (PDT) References: In-Reply-To: Content-Language: en-gb Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hi, Well... I have some new and interesting information.=20 After deleting the file, and re-creating from backup, the file system g= ot mounted read only and the following errors were logged: May 8 14:58:15 despair kernel: EXT4-fs error (device dm-0): mb_free_bl= ocks:1411: group 5124block 167904376:freeing already freed block (bit 1= 144) May 8 14:58:15 despair kernel: Aborting journal on device dm-0-8. May 8 14:58:15 despair kernel: EXT4-fs (dm-0): Remounting filesystem r= ead-only May 8 14:58:15 despair kernel: EXT4-fs error (device dm-0): m= b_free_blocks:1411: group 5124block 167904377:freeing already freed blo= ck (bit 1145) May 8 14:58:15 despair kernel: EXT4-fs error (device dm-= 0): mb_free_blocks:1411: group 5124block 167904378:freeing already free= d block (bit 1146) May 8 14:58:15 despair kernel: EXT4-fs error (devic= e dm-0): mb_free_blocks:1411: group 5124block 167904379:freeing already= freed block (bit 1147) May 8 14:58:15 despair kernel: EXT4-fs error (= device dm-0): mb_free_blocks:1411: group 5124block 167904380:freeing al= ready freed block (bit 1148) May 8 14:58:15 despair kernel: EXT4-fs er= ror (device dm-0): mb_free_blocks:1411: group 5124block 167904381:freei= ng already freed block (bit 1149) May 8 14:58:15 despair kernel: EXT4-= fs error (device dm-0): mb_free_blocks:1411: group 5124block 167904382:= freeing already freed block (bit 1150) May 8 14:58:16 despair kernel: = EXT4-fs error (device dm-0): mb_free_blocks:1411: group 5124block 16790= 4383:freeing already freed block (bit 1151) May 8 14:58:16 despair ker= nel: EXT4-fs error (device dm-0): mb_free_blocks:1411: group 5124block = 167904384:freeing already freed block (bit 1152) May 8 14:58:16 despai= r kernel: EXT4-fs error (device dm-0): mb_free_blocks:1411: group 5124b= lock 167904385:freeing already freed block (bit 1153) May 8 14:58:16 d= espair kernel: EXT4-fs error (device dm-0): mb_free_blocks:1411: group = 5124block 167904386:freeing already freed block (bit 1154) May 8 14:58= :16 despair kernel: EXT4-fs error (device dm-0): mb_free_blocks:1411: g= roup 5125block 167949296:freeing already freed block (bit 13296) May 8= 14:58:16 despair kernel: EXT4-fs error (device dm-0): mb_free_blocks:1= 411: group 5125block 167949297:freeing already freed block (bit 13297) = May 8 14:58:16 despair kernel: EXT4-fs error (device dm-0): mb_free_bl= ocks:1411: group 5125block 167949298:freeing already freed block (bit 1= 3298) May 8 14:58:16 despair kernel: EXT4-fs error (device dm-0): mb_f= ree_blocks:1411: group 5125block 167949299:freeing already freed block = (bit 13299) May 8 14:58:17 despair kernel: EXT4-fs error (device dm-0)= : mb_free_blocks:1411: group 5125block 167949300:freeing already freed = block (bit 13300) May 8 14:58:17 despair kernel: EXT4-fs error (device= dm-0): mb_free_blocks:1411: group 5125block 167949301:freeing already = freed block (bit 13301) May 8 14:58:17 despair kernel: EXT4-fs error (= device dm-0): mb_free_blocks:1411: group 5125block 167949302:freeing al= ready freed block (bit 13302) May 8 14:58:17 despair kernel: EXT4-fs e= rror (device dm-0): mb_free_blocks:1411: group 5125block 167949303:free= ing already freed block (bit 13303) May 8 14:58:17 despair kernel: EXT= 4-fs error (device dm-0): mb_free_blocks:1411: group 5125block 16794930= 4:freeing already freed block (bit 13304) May 8 14:58:17 despair kerne= l: EXT4-fs error (device dm-0): mb_free_blocks:1411: group 5125block 16= 7949305:freeing already freed block (bit 13305) May 8 14:58:17 despair= kernel: EXT4-fs error (device dm-0): mb_free_blocks:1411: group 5125bl= ock 167949306:freeing already freed block (bit 13306) These are the same blocks slated as multiply claimed :) And then running an FSCK, we got the following: ***** File system check forced at Wed May 8 15:16:50 WEST 2013 ***** f= sck 1.41.14 (22-Dec-2010) e2fsck 1.42.3 (14-May-2012) /dev/c/c: recovering journal Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory s= tructure Pass 3: Checking directory connectivity Pass 4: Checking refer= ence counts Pass 5: Checking group summary information Free blocks coun= t wrong for group #5124 (28170, counted=3D28159). =46ix? yes =46ree blocks count wrong for group #5125 (25861, counted=3D25850). =46ix? yes =46ree blocks count wrong (420683133, counted=3D420644972). =46ix? yes =46ree inodes count wrong (29595347, counted=3D29595271). =46ix? yes /dev/c/c: ***** FILE SYSTEM WAS MODIFIED ***** /dev/c/c: 616825/30212096 files (13.6% non-contiguous), 62748564/483393= 536 blocks Volume seems clean now after reboot and keeps coming back clean. Any ideas based on this? The old Database was over 1.6 GB in size. The = re-created one from backup is much smaller 33MB (as it was compacted be= fore restoring). Once these DB files grow they don't get smaller until = compacted. Although I'm sure file size should not have a bearing on thi= s. Many Thanks Stephen Elliott =46rom: Stephen Elliott [mailto:techweb@ntlworld.com] Sent: 26 April 2013 22:37 To: 'linux-ext4@vger.kernel.org' Subject: FSCK Errors Hi all, Just rebooted my box today after 200 days uptime and thought I'd reques= t a volume scan and it found errors! I've never had a power outage etc = so am keen to know what could have caused this file system corruption? = Anyu ideas??? I'm running 4.2.21 on a ReadyNAS Pro6, but ultimately it is a Linux (De= bian) 2.6.37.6. based system underneath.=20 ***** File system check forced at Fri Apr 26 20:08:38 WEST 2013 ***** f= sck 1.41.14 (22-Dec-2010) e2fsck 1.42.3 (14-May-2012) Pass 1: Checking = inodes, blocks, and sizes Inode 4195619, i_blocks is 3135728, should be= 3135904. Fix? yes Running additional passes to resolve blocks claimed by more than one in= ode... Pass 1B: Rescanning for multiply-claimed blocks Multiply-claimed block(= s) in inode 4195619: 167904376 167904377 167904378 167904379 167904380 = 167904381 167904382 167904383 167904384 167904385 167904386 167949296 1= 67949297 167949298 167949299 167949300 167949301 167949302 167949303 16= 7949304 167949305 167949306 Pass 1C: Scanning directories for inodes wi= th multiply-claimed blocks Pass 1D: Reconciling multiply-claimed blocks= (There are 1 inodes containing multiply-claimed blocks.) =46ile /PREMIER/Premier Automation Purchase OrdersApp V18.5.mdb (inode = #4195619, mod time Fri Apr 26 20:07:42 2013) has 22 multiply-claimed bl= ock(s), shared with 0 file(s): Multiply-claimed blocks already reassigned or cloned. Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/c/c: ***** FILE SYSTEM WAS MODIFIED ***** /dev/c/c: 615898/30212096 files (13.6% non-contiguous), 62353456/483393= 536 blocks I'm curious to know what this is all about, shared with 0 files!!!!: =46ile /PREMIER/Premier Automation Purchase OrdersApp V18.5.mdb (inode = #4195619, mod time Fri Apr 26 20:07:42 2013) has 22 multiply-claimed bl= ock(s), shared with 0 file(s): Multiply-claimed blocks already reassigned or cloned. Every follow on boot with FSCK yields the following: ***** File system check forced at Fri Apr 26 20:21:42 WEST 2013 ***** f= sck 1.41.14 (22-Dec-2010) e2fsck 1.42.3 (14-May-2012) Pass 1: Checking = inodes, blocks, and sizes Running additional passes to resolve blocks claimed by more than one in= ode... Pass 1B: Rescanning for multiply-claimed blocks Multiply-claimed block(= s) in inode 4195619: 167904376 167904377 167904378 167904379 167904380 = 167904381 167904382 167904383 167904384 167904385 167904386 167949296 1= 67949297 167949298 167949299 167949300 167949301 167949302 167949303 16= 7949304 167949305 167949306 Pass 1C: Scanning directories for inodes wi= th multiply-claimed blocks Pass 1D: Reconciling multiply-claimed blocks= (There are 1 inodes containing multiply-claimed blocks.) =46ile /PREMIER/Premier Automation Purchase OrdersApp V18.5.mdb (inode = #4195619, mod time Fri Apr 26 20:07:42 2013) has 22 multiply-claimed block(s), shared with 0 file(s): Multiply-claimed blocks already reassigned or cloned. Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/c/c: 615898/30212096 files (13.6% non-contiguous), 62353456/483393= 536 blocks Still same thing with multiply claimed blocks :)=E2=98=B9 Any ideas? Many Thanks Stephen Elliott=20 -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html