September 1, 201312 yr unraid 5.0-rc11 (was going to upgrade to 5.0 but found some errors I first want to fix before upgrading) Got many errors in the smart report of my parity drive last week so I swapped it for a new one. Parity was build again and a (non correcting) parity check done. It found some errors. I did another parity check and had the errors corrected. Then I did another (non correcting) check : this time no errors. But now, (1 day later), I get following in my syslog when I try to browse in finder through some folders on my server : Sep 1 20:30:16 Tower shfs/user: shfs_write: write: (5) Input/output error Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/VMware/Temporary Items/.AppleDouble/.Parent (30) Read-only file system5 root 20 0 0 0 0 S 0 0.0 0:00.00 scsi_eh_3 Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/VMware/.AppleDesktop/.volinfo (30) Read-only file system Sep 1 20:30:16 Tower kernel: REISERFS error (device md4): reiserfs-2025 reiserfs_cache_bitmap_metadata: bitmap block 100302848 is corrupted: first bit must be 1 0 S 0 0.0 0:00.00 scsi_eh_4 Sep 1 20:30:16 Tower kernel: REISERFS (device md4): Remounting filesystem read-only Sep 1 20:30:16 Tower kernel: REISERFS warning (device md4): clm-6006 reiserfs_dirty_inode: writing inode 1726 on readonly FS Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Software/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Software/Network Trash Folder/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Software/Temporary Items/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Software/.AppleDesktop/.volinfo (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Pictures/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Pictures/Network Trash Folder/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Pictures/Temporary Items/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Pictures/.AppleDesktop/.volinfo (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/NeedsToBeSorted/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/NeedsToBeSorted/Network Trash Folder/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/NeedsToBeSorted/Temporary Items/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/NeedsToBeSorted/.AppleDesktop/.volinfo (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Music/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Music/Network Trash Folder/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Music/Temporary Items/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Music/.AppleDesktop/.volinfo (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Movies/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Movies/Network Trash Folder/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Movies/Temporary Items/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Movies/.AppleDesktop/.volinfo (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Books and Magazines/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Books and Magazines/Network Trash Folder/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Books and Magazines/Temporary Items/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Books and Magazines/.AppleDesktop/.volinfo (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Backup/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Backup/Network Trash Folder/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Backup/Temporary Items/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Backup/.AppleDesktop/.volinfo (30) Read-only file system Found this page : http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems and ran a check : reiserfsck --check /dev/md4 Output : root@Tower:~# reiserfsck --check /dev/md4 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/md4 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Sun Sep 1 20:45:02 2013 ########### Replaying journal: Trans replayed: mountid 155, transid 11186, desc 3991, len 1, commit 3993, next trans offset 3976 Trans replayed: mountid 155, transid 11187, desc 3994, len 1, commit 3996, next trans offset 3979 Trans replayed: mountid 155, transid 11188, desc 3997, len 1, commit 3999, next trans offset 3982 Trans replayed: mountid 155, transid 11189, desc 4000, len 9, commit 4010, next trans offset 3993 Trans replayed: mountid 155, transid 11190, desc 4011, len 1, commit 4013, next trans offset 3996 Trans replayed: mountid 155, transid 11191, desc 4014, len 8, commit 4023, next trans offset 4006 Trans replayed: mountid 155, transid 11192, desc 4024, len 8, commit 4033, next trans offset 4016 Trans replayed: mountid 155, transid 11193, desc 4034, len 9, commit 4044, next trans offset 4027 Replaying journal: Done. Reiserfs journal '/dev/md4' in blocks [18..8211]: 8 transactions replayed Checking internal tree.. \/ 1 (of 4|/ 80 (of 170\/ 61 (of 156|bad_path: The left delimiting key [32 33 0x57001 IND (1)] of the node (100302849) must be equal to the first element's key [15950 15964 0x4c5fe001 IND (1)] within the node. / 62 (of 156/bad_path: The left delimiting key [32 33 0x44b001 IND (1)] of the node (100302850) must be equal to the first element's key [15950 15964 0x4ea22001 IND (1)] within the node. / 63 (of 156-bad_indirect_item: block 100302851: The item (15950 15964 0x4ee26001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (173) to the block (100301865), which is in tree already bad_indirect_item: block 100302851: The item (15950 15964 0x4ee26001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (174) to the block (100301862), which is in tree already bad_indirect_item: block 100302851: The item (15950 15964 0x4ee26001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (221) to the block (100301849), which is in tree already ... bad_indirect_item: block 102191267: The item (85 86 0x1fdecd001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (202) to the block (100302798), which is in tree already bad_indirect_item: block 102191267: The item (85 86 0x1fdecd001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (203) to the block (100302799), which is in tree already finished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 4 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Sun Sep 1 20:54:30 2013 ########### root@Tower:~# I read that this --rebuild-tree is last resort only. Can I run it or should I do something else first? syslog.txt
Archived
This topic is now archived and is closed to further replies.