From: bugzilla-daemon@bugzilla.kernel.org
To: reiserfs-devel@vger.kernel.org
Subject: [Bug 29162] Reiserfs hang with dataloss sometimes
Date: Sat, 11 May 2013 15:03:37 +0000 (UTC) [thread overview]
Message-ID: <20130511150337.E3DD711FA6B@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-29162-695@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=29162
--- Comment #45 from Ra√∫l <rasasi78@gmail.com> 2013-05-11 15:03:36 ---
Hi:
I've run into a series of locks of this kind. I can't add much more to what
I've already reported. I haven't found a method of reliably reproduce this
lock, my impression so far is that this one is related to:
a) wake up from suspend to ram (maybe also to disk) and
b) certain /corruption/ layout in disk
Latest locks happened after I resume from ram. Disk was not much loaded at the
lock moment, there was a high user activity though: like running and closing
apps, email and an important amount of download threads in the background. I
had the lock there.
As usual, the cleanest way to get out of this was alt-sysrq-E that terms all
processes. Then three finger salute.
On a fresh boot, I tried the same usage pattern, soon after I had the lock
again. In this case STR or STD (Suspend to Disk) weren't involved.
I decided to go into a reiserfsck --rebuild-tree in my home partition. This is
a log excerpt:
"""
Replaying journal: Done.
Reiserfs journal '/dev/mapper/portaka-home' in blocks [18..8211]: 0
transactions replayed
###########
reiserfsck --rebuild-tree started at Fri May 10 11:04:30 2013
###########
Pass 0:
####### Pass 0 #######
Loading on-disk bitmap .. ok, 43532529 blocks marked used
Skipping 9574 blocks (super block, journal, bitmaps) 43522955 blocks will be
read
0%...block 6328224: The number of items (34381) is incorrect, should be (1) -
corrected
block 6328224: The free space (15751) is incorrect, should be (2256) -
corrected
pass0: vpf-10110: block 6328224, item (0): Unknown item type found [2130706432
1023807744 0x3d970000 ??? (13)] - deleted
block 6343857: The number of items (34381) is incorrect, should be (1) -
corrected
block 6343857: The free space (15751) is incorrect, should be (2256) -
corrected
pass0: vpf-10110: block 6343857, item (0): Unknown item type found [2130706432
1023807744 0x3d970000 ??? (13)] - deleted
.20%...block 15040910: The number of items (34826) is incorrect, should be (1)
- corrected
block 15040910: The free space (2) is incorrect, should be (4048) - corrected
pass0: vpf-10110: block 15040910, item (0): Unknown item type found [3506543104
3523215796 0xa3000784 ??? (15)] - deleted
.block 16215906: The number of items (287) is incorrect, should be (1) -
corrected
block 16215906: The free space (0) is incorrect, should be (4048) - corrected
pass0: vpf-10200: block 16215906, item 0: The item [218104576 203714 0x790e01
IND (1)] with wrong offset is deleted
block 17156098: The number of items (12648) is incorrect, should be (1) -
corrected
block 17156098: The free space (0) is incorrect, should be (4048) - corrected
40%block 18917377: The number of items (6) is incorrect, should be (0) -
corrected
block 18917377: The free space (15481) is incorrect, should be (4072) -
corrected
block 19611181: The number of items (6) is incorrect, should be (0) - corrected
block 19611181: The free space (15481) is incorrect, should be (4072) -
corrected
.block 20333852: The number of items (15) is incorrect, should be (1) -
corrected
block 20333852: The free space (0) is incorrect, should be (3792) - corrected
pass0: vpf-10210: block 20333852, item 0: The item with wrong offset or length
found [4608 16778752 0x63030000 DRCT (2)], len 256 - deleted
..block 25257511: The number of items (287) is incorrect, should be (1) -
corrected
block 25257511: The free space (29793) is incorrect, should be (4048) -
corrected
pass0: vpf-10200: block 25257511, item 0: The item [218103998 65810 0x6e0e01
IND (1)] with wrong offset is deleted
.60%block 28012850: The number of items (41488) is incorrect, should be (1) -
corrected
block 28012850: The free space (24) is incorrect, should be (4048) - corrected
pass0: vpf-10110: block 28012850, item (0): Unknown item type found [38049792
1032720128 0x10010002 ??? (15)] - deleted
.block 30356195: The number of items (282) is incorrect, should be (1) -
corrected
block 30356195: The free space (0) is incorrect, should be (2256) - corrected
pass0: vpf-10110: block 30356195, item (0): Unknown item type found [205917185
285212679 0x1 ??? (15)] - deleted
.block 30911284: The number of items (12648) is incorrect, should be (1) -
corrected
block 30911284: The free space (0) is incorrect, should be (4048) - corrected
block 31013511: The number of items (6) is incorrect, should be (0) - corrected
block 31013511: The free space (1472) is incorrect, should be (4072) -
corrected
block 31038991: The number of items (6) is incorrect, should be (0) - corrected
block 31038991: The free space (1472) is incorrect, should be (4072) -
corrected
.block 33620308: The number of items (15) is incorrect, should be (1) -
corrected
block 33620308: The free space (0) is incorrect, should be (3792) - corrected
pass0: vpf-10210: block 33620308, item 0: The item with wrong offset or length
found [4608 16778752 0x63030000 DRCT (2)], len 256 - deleted
.block 34356027: The number of items (282) is incorrect, should be (1) -
corrected
block 34356027: The free space (0) is incorrect, should be (2256) - corrected
pass0: vpf-10110: block 34356027, item (0): Unknown item type found [205917185
285212679 0x1 ??? (15)] - deleted
block 34621658: The number of items (4352) is incorrect, should be (1) -
corrected
block 34621658: The free space (39937) is incorrect, should be (207) -
corrected
pass0: vpf-10110: block 34621658, item (0): Unknown item type found [218169345
114 0x1180001 ??? (15)] - deleted
"""
I wonder if those "Unknown item type found" or several of those poiting to same
block, e.g.: 205917185 mean anything or could trigger the unexpected lock.
HTH,
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.--
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
next prev parent reply other threads:[~2013-05-11 15:03 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 9:36 [Bug 29162] New: Reiserfs hang with dataloss sometimes bugzilla-daemon
2011-02-15 9:38 ` [Bug 29162] " bugzilla-daemon
2011-02-15 9:39 ` bugzilla-daemon
2011-02-15 9:39 ` bugzilla-daemon
2011-02-15 9:41 ` bugzilla-daemon
2011-02-15 9:44 ` bugzilla-daemon
2011-02-15 9:45 ` bugzilla-daemon
2011-02-15 9:47 ` bugzilla-daemon
2011-03-08 20:44 ` bugzilla-daemon
2011-03-15 3:13 ` bugzilla-daemon
2011-03-15 22:03 ` bugzilla-daemon
2011-03-28 9:33 ` bugzilla-daemon
2011-04-17 18:08 ` bugzilla-daemon
2011-05-02 16:11 ` bugzilla-daemon
2011-05-11 14:54 ` bugzilla-daemon
2011-05-13 13:09 ` bugzilla-daemon
2011-05-17 7:16 ` bugzilla-daemon
2011-05-17 9:19 ` bugzilla-daemon
2011-05-17 13:15 ` bugzilla-daemon
2011-05-21 14:37 ` bugzilla-daemon
2011-05-21 14:38 ` bugzilla-daemon
2011-05-22 11:06 ` bugzilla-daemon
2011-05-23 13:06 ` bugzilla-daemon
2011-05-23 13:11 ` bugzilla-daemon
2011-05-23 16:33 ` bugzilla-daemon
2011-05-23 16:35 ` bugzilla-daemon
2011-05-23 16:38 ` bugzilla-daemon
2011-05-23 18:54 ` bugzilla-daemon
2011-05-23 20:02 ` bugzilla-daemon
2011-06-07 14:23 ` bugzilla-daemon
2011-06-10 12:41 ` bugzilla-daemon
2011-06-11 17:29 ` bugzilla-daemon
2011-06-11 17:32 ` bugzilla-daemon
2011-06-13 15:10 ` bugzilla-daemon
2011-06-13 21:37 ` bugzilla-daemon
2011-06-14 9:14 ` bugzilla-daemon
2011-06-14 9:16 ` bugzilla-daemon
2011-06-20 7:38 ` bugzilla-daemon
2011-08-21 13:00 ` bugzilla-daemon
2011-08-21 14:11 ` bugzilla-daemon
2011-08-21 15:18 ` bugzilla-daemon
2011-08-22 12:34 ` bugzilla-daemon
2011-09-08 12:48 ` bugzilla-daemon
2012-02-06 18:57 ` bugzilla-daemon
2012-04-12 11:32 ` bugzilla-daemon
2012-06-06 8:32 ` bugzilla-daemon
2013-02-11 22:17 ` bugzilla-daemon
2013-02-18 19:45 ` bugzilla-daemon
2013-02-27 9:27 ` bugzilla-daemon
2013-03-02 10:36 ` bugzilla-daemon
2013-04-17 12:17 ` bugzilla-daemon
2013-05-11 15:03 ` bugzilla-daemon [this message]
2013-05-11 15:23 ` bugzilla-daemon
2013-05-11 15:51 ` bugzilla-daemon
2013-05-11 16:11 ` bugzilla-daemon
2013-05-30 21:54 ` bugzilla-daemon
2013-05-30 21:55 ` bugzilla-daemon
2013-09-20 19:23 ` bugzilla-daemon
2013-09-21 23:39 ` bugzilla-daemon
2013-12-18 21:01 ` bugzilla-daemon
2013-12-18 21:08 ` bugzilla-daemon
2013-12-20 22:41 ` bugzilla-daemon
2013-12-20 22:44 ` bugzilla-daemon
2014-01-05 19:47 ` bugzilla-daemon
2014-01-05 22:02 ` bugzilla-daemon
2014-01-06 16:05 ` bugzilla-daemon
2014-01-06 16:07 ` bugzilla-daemon
2014-01-06 18:45 ` bugzilla-daemon
2014-01-28 21:45 ` bugzilla-daemon
2014-02-04 20:20 ` bugzilla-daemon
2014-02-04 20:21 ` bugzilla-daemon
2014-02-04 20:22 ` bugzilla-daemon
2015-02-25 21:22 ` bugzilla-daemon
2015-04-07 10:05 ` bugzilla-daemon
2015-04-07 16:03 ` bugzilla-daemon
2016-02-16 22:05 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130511150337.E3DD711FA6B@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).