LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices

Reply
 
Search this Thread
Old 04-26-2013, 05:10 PM   #1
steveoelliott
LQ Newbie
 
Registered: May 2005
Posts: 15

Rep: Reputation: 0
FSCK Errors - Multiply Claimed Blocks.


Hi all,

Just rebooted my box today after 200 days uptime and thought I'd request 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 (Debian) 2.6.37.6. based system underneath.

***** File system check forced at Fri Apr 26 20:08:38 WEST 2013 ***** fsck 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 inode...
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 167949297 167949298 167949299 167949300 167949301 167949302 167949303 167949304 167949305 167949306 Pass 1C: Scanning directories for inodes with multiply-claimed blocks Pass 1D: Reconciling multiply-claimed blocks (There are 1 inodes containing multiply-claimed blocks.)

File /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: ***** FILE SYSTEM WAS MODIFIED *****
/dev/c/c: 615898/30212096 files (13.6% non-contiguous), 62353456/483393536 blocks

I'm curious to know what this is all about, shared with 0 files!!!!:

File /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.


Every follow on boot with FSCK yields the following:


***** File system check forced at Fri Apr 26 20:21:42 WEST 2013 ***** fsck 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 inode...
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 167949297 167949298 167949299 167949300 167949301 167949302 167949303 167949304 167949305 167949306 Pass 1C: Scanning directories for inodes with multiply-claimed blocks Pass 1D: Reconciling multiply-claimed blocks (There are 1 inodes containing multiply-claimed blocks.)

File /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/483393536 blocks

Still same thing with multiply claimed blocks

Any ideas?
 
Old 04-26-2013, 08:24 PM   #2
steveoelliott
LQ Newbie
 
Registered: May 2005
Posts: 15

Original Poster
Rep: Reputation: 0
Just to further add, SMART logs are clean. No sectors reallocated or ATA errors.
 
Old 04-28-2013, 03:22 PM   #3
steveoelliott
LQ Newbie
 
Registered: May 2005
Posts: 15

Original Poster
Rep: Reputation: 0
Anybody able to advise???
 
Old 04-28-2013, 04:02 PM   #4
PTrenholme
Senior Member
 
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 4,147

Rep: Reputation: 330Reputation: 330Reputation: 330Reputation: 330
Which file system are you using? (ext?, btrfs, ???).

I've seen similar problems when a journal file failed to update the file, but it's quite rare and fsck usually fixes it.

Can you boot from a rescue system and run fsck manually (without the automatic fix options) to see if you can get more details?

What happens if you restore the file from its current backup? That should put the whole file on a different inode set.
 
Old 04-28-2013, 04:08 PM   #5
steveoelliott
LQ Newbie
 
Registered: May 2005
Posts: 15

Original Poster
Rep: Reputation: 0
It's EXT4 and is actually part of a ReadyNAS Pro 6 system. I have ran the FSCK manually via console and same thing every time. Strange as it comes back clean.

I can delete and re-add if necessary. But... Given the fact it says shared with "0" files, I suspect it is a bogus error.

Am just keen to know why this happened really and possible causes. In addition, knowing how to correct it without deleting / restoring would be interesting.

Last edited by steveoelliott; 04-28-2013 at 04:10 PM.
 
Old 04-29-2013, 06:37 PM   #6
steveoelliott
LQ Newbie
 
Registered: May 2005
Posts: 15

Original Poster
Rep: Reputation: 0
Anybody have any further feedback???
 
Old 04-30-2013, 02:51 AM   #7
nigelc
Member
 
Registered: Oct 2004
Location: Sydney, Australia
Distribution: Mageia 4
Posts: 297
Blog Entries: 4

Rep: Reputation: 52
do a touch /forcefsck in the / dir.
Then reboot.
If it gets no errors then it's ok.
 
Old 04-30-2013, 02:56 AM   #8
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
You could run a SMART long test using smartctl.
 
Old 04-30-2013, 03:15 AM   #9
steveoelliott
LQ Newbie
 
Registered: May 2005
Posts: 15

Original Poster
Rep: Reputation: 0
The /forcefsck option is no different to my maual FSCK by unmounting the partition but thanks anyway.

I may consider the extended smart option. Although given the activity on the box, I would expect the standard stats to have flagged something especially as I did a RAID sync only the other day.
 
Old 05-08-2013, 10:26 AM   #10
steveoelliott
LQ Newbie
 
Registered: May 2005
Posts: 15

Original Poster
Rep: Reputation: 0
Hi,

Well... I have some new and interesting information.

After deleting the file, and re-creating from backup, the file system got mounted read only and the following errors were logged:]

May 8 14:58:15 despair kernel: EXT4-fs error (device dm-0): mb_free_blocks:1411: group 5124block 167904376:freeing already freed block (bit 1144)
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 read-only
May 8 14:58:15 despair kernel: EXT4-fs error (device dm-0): mb_free_blocks:1411: group 5124block 167904377:freeing already freed block (bit 1145)
May 8 14:58:15 despair kernel: EXT4-fs error (device dm-0): mb_free_blocks:1411: group 5124block 167904378:freeing already freed block (bit 1146)
May 8 14:58:15 despair kernel: EXT4-fs error (device 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 already freed block (bit 1148)
May 8 14:58:15 despair kernel: EXT4-fs error (device dm-0): mb_free_blocks:1411: group 5124block 167904381:freeing 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 167904383:freeing already freed block (bit 1151)
May 8 14:58:16 despair kernel: EXT4-fs error (device dm-0): mb_free_blocks:1411: group 5124block 167904384:freeing already freed block (bit 1152)
May 8 14:58:16 despair kernel: EXT4-fs error (device dm-0): mb_free_blocks:1411: group 5124block 167904385:freeing already freed block (bit 1153)
May 8 14:58:16 despair 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: group 5125block 167949296:freeing already freed block (bit 13296)
May 8 14:58:16 despair kernel: EXT4-fs error (device dm-0): mb_free_blocks:1411: group 5125block 167949297:freeing already freed block (bit 13297)
May 8 14:58:16 despair kernel: EXT4-fs error (device dm-0): mb_free_blocks:1411: group 5125block 167949298:freeing already freed block (bit 13298)
May 8 14:58:16 despair kernel: EXT4-fs error (device dm-0): mb_free_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 already freed block (bit 13302)
May 8 14:58:17 despair kernel: EXT4-fs error (device dm-0): mb_free_blocks:1411: group 5125block 167949303:freeing already freed block (bit 13303)
May 8 14:58:17 despair kernel: EXT4-fs error (device dm-0): mb_free_blocks:1411: group 5125block 167949304:freeing already freed block (bit 13304)
May 8 14:58:17 despair kernel: EXT4-fs error (device dm-0): mb_free_blocks:1411: group 5125block 167949305:freeing already freed block (bit 13305)
May 8 14:58:17 despair kernel: EXT4-fs error (device dm-0): mb_free_blocks:1411: group 5125block 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 ***** fsck 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 structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Free blocks count wrong for group #5124 (28170, counted=28159).
Fix? yes

Free blocks count wrong for group #5125 (25861, counted=25850).
Fix? yes

Free blocks count wrong (420683133, counted=420644972).
Fix? yes

Free inodes count wrong (29595347, counted=29595271).
Fix? yes


/dev/c/c: ***** FILE SYSTEM WAS MODIFIED *****
/dev/c/c: 616825/30212096 files (13.6% non-contiguous), 62748564/483393536 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 before 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 this.

Many Thanks
Stephen Elliott
 
Old 10-16-2013, 06:53 AM   #11
steveoelliott
LQ Newbie
 
Registered: May 2005
Posts: 15

Original Poster
Rep: Reputation: 0
Hi all,

I later found that rebooting the server whilst the MS access DB was open on client computers seemed to cause these issues. I'm surprised though as Samba and the server were shutdown cleanly so whilst have the DB open at the time from client computers may cause corruption of the DB, I don't see why it should corrupt the FS.

Thanks...
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
FSCK multiply-claimed blocks cbtshare Linux - Server 1 04-01-2010 06:51 AM
fsck is not removing bad blocks, why not? exceed1 Linux - General 9 03-21-2008 08:07 AM
automatic fsck on boot. fsck errors. nixel Slackware 1 05-17-2004 07:51 AM
fsck errors LazloH Linux - Software 3 05-13-2004 11:45 AM
fsck many bad blocks mjolnir *BSD 5 01-13-2004 06:35 AM


All times are GMT -5. The time now is 04:40 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration