* reiser4+2.6.38.6 broken? @ 2011-05-16 19:55 Volker Armin Hemmann 2011-05-16 20:16 ` Edward Shishkin 0 siblings, 1 reply; 7+ messages in thread From: Volker Armin Hemmann @ 2011-05-16 19:55 UTC (permalink / raw) To: reiserfs-devel Hi, I have several r4 partitions, all with cryptcompress. I tried 2.6.38.x6 a few hours ago - after 3h I looked at dmesg and it was swamped with error messages and tracebacks. Sadly I tried to run fsck before saving dmesg - and the box froze completely. I am now back to 2.6.36.4. fsck is running on one of the partitions. Meanwhile I see tons of this: [ 153.379751] reiser4[kuiserver(2649)]: reiser4_inflate_cluster (fs/reiser4/plugin/file/cryptcompress.c:1136)[edward-1460]: [ 153.379756] WARNING: Inode 2975012: disk cluster 27 looks corrupted [ 163.301372] reiser4[kuiserver(2669)]: dc_check_checksum (fs/reiser4/plugin/file/cryptcompress.c:969)[edward-156]: [ 163.301374] WARNING: Bad disk cluster checksum 799645291, (should be 546616041) Fsck? [ 163.301375] [ 163.301378] reiser4[kuiserver(2669)]: reiser4_inflate_cluster (fs/reiser4/plugin/file/cryptcompress.c:1136)[edward-1460]: [ 163.301379] WARNING: Inode 2975012: disk cluster 27 looks corrupted [ 384.552095] chrome_sandbox (2789): /proc/2786/oom_adj is deprecated, please use /proc/2786/oom_score_adj instead. [ 666.688727] reiser4[ent:md1!(1383)]: dc_check_checksum (fs/reiser4/plugin/file/cryptcompress.c:969)[edward-156]: [ 666.688732] WARNING: Bad disk cluster checksum 1953788261, (should be 1187109005) Fsck? [ 666.688736] [ 666.688748] reiser4[ent:md1!(1383)]: reiser4_inflate_cluster (fs/reiser4/plugin/file/cryptcompress.c:1136)[edward-1460]: [ 666.688752] WARNING: Inode 2975012: disk cluster 21 looks corrupted [ 666.688762] reiser4[ent:md1!(1383)]: read_some_cluster_pages (fs/reiser4/plugin/file/cryptcompress.c:2328)[edward-219]: [ 666.688767] WARNING: do_readpage_ctail failed [ 666.688780] reiser4[ent:md1!(1383)]: capture_anon_pages (fs/reiser4/plugin/file/cryptcompress.c:3518)[edward-1077]: [ 666.688784] WARNING: Capture failed (inode 2975012, result=-5, captured=16) [ 666.688788] [ 903.921155] reiser4[konqueror(3060)]: key_warning (fs/reiser4/plugin/file_plugin_common.c:511)[nikita-717]: [ 903.921160] WARNING: Error for inode 5984667 (-2) and [ 1604.433805] reiser4[konqueror(3181)]: key_warning (fs/reiser4/plugin/file_plugin_common.c:511)[nikita-717]: [ 1604.433810] WARNING: Error for inode 4743057 (-2) [ 1949.251123] reiser4[konqueror(3248)]: key_warning (fs/reiser4/plugin/file_plugin_common.c:511)[nikita-717]: [ 1949.251125] WARNING: Error for inode 4743057 (-2) known problem with 2.6.38.X? Glück Auf, Volker -- 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: reiser4+2.6.38.6 broken? 2011-05-16 19:55 reiser4+2.6.38.6 broken? Volker Armin Hemmann @ 2011-05-16 20:16 ` Edward Shishkin [not found] ` <1725025.DC6atdjbiy@localhost> 0 siblings, 1 reply; 7+ messages in thread From: Edward Shishkin @ 2011-05-16 20:16 UTC (permalink / raw) To: Volker Armin Hemmann; +Cc: reiserfs-devel On 05/16/2011 09:55 PM, Volker Armin Hemmann wrote: > Hi, > > I have several r4 partitions, all with cryptcompress. > > I tried 2.6.38.x6 a few hours ago - after 3h I looked at dmesg and it was > swamped with error messages and tracebacks. Sadly I tried to run fsck before > saving dmesg - and the box froze completely. > > I am now back to 2.6.36.4. fsck is running on one of the partitions. Meanwhile > I see tons of this: > > [ 153.379751] reiser4[kuiserver(2649)]: reiser4_inflate_cluster > (fs/reiser4/plugin/file/cryptcompress.c:1136)[edward-1460]: > [ 153.379756] WARNING: Inode 2975012: disk cluster 27 looks corrupted > [ 163.301372] reiser4[kuiserver(2669)]: dc_check_checksum > (fs/reiser4/plugin/file/cryptcompress.c:969)[edward-156]: > [ 163.301374] WARNING: Bad disk cluster checksum 799645291, (should be > 546616041) Fsck? > [ 163.301375] > [ 163.301378] reiser4[kuiserver(2669)]: reiser4_inflate_cluster > (fs/reiser4/plugin/file/cryptcompress.c:1136)[edward-1460]: > [ 163.301379] WARNING: Inode 2975012: disk cluster 27 looks corrupted > [ 384.552095] chrome_sandbox (2789): /proc/2786/oom_adj is deprecated, please > use /proc/2786/oom_score_adj instead. > [ 666.688727] reiser4[ent:md1!(1383)]: dc_check_checksum > (fs/reiser4/plugin/file/cryptcompress.c:969)[edward-156]: > [ 666.688732] WARNING: Bad disk cluster checksum 1953788261, (should be > 1187109005) Fsck? > [ 666.688736] > [ 666.688748] reiser4[ent:md1!(1383)]: reiser4_inflate_cluster > (fs/reiser4/plugin/file/cryptcompress.c:1136)[edward-1460]: > [ 666.688752] WARNING: Inode 2975012: disk cluster 21 looks corrupted > [ 666.688762] reiser4[ent:md1!(1383)]: read_some_cluster_pages > (fs/reiser4/plugin/file/cryptcompress.c:2328)[edward-219]: > [ 666.688767] WARNING: do_readpage_ctail failed > [ 666.688780] reiser4[ent:md1!(1383)]: capture_anon_pages > (fs/reiser4/plugin/file/cryptcompress.c:3518)[edward-1077]: > [ 666.688784] WARNING: Capture failed (inode 2975012, result=-5, captured=16) > [ 666.688788] > [ 903.921155] reiser4[konqueror(3060)]: key_warning > (fs/reiser4/plugin/file_plugin_common.c:511)[nikita-717]: > [ 903.921160] WARNING: Error for inode 5984667 (-2) > > and > > [ 1604.433805] reiser4[konqueror(3181)]: key_warning > (fs/reiser4/plugin/file_plugin_common.c:511)[nikita-717]: > [ 1604.433810] WARNING: Error for inode 4743057 (-2) > [ 1949.251123] reiser4[konqueror(3248)]: key_warning > (fs/reiser4/plugin/file_plugin_common.c:511)[nikita-717]: > [ 1949.251125] WARNING: Error for inode 4743057 (-2) > > known problem with 2.6.38.X? Yes, this is known and old problem. This is not specific to compression. Edward. > > Glück Auf, > Volker > -- > 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 -- 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
[parent not found: <1725025.DC6atdjbiy@localhost>]
* Re: reiser4+2.6.38.6 broken? [not found] ` <1725025.DC6atdjbiy@localhost> @ 2011-05-16 20:33 ` Edward Shishkin 2011-05-16 21:12 ` Volker Armin Hemmann 0 siblings, 1 reply; 7+ messages in thread From: Edward Shishkin @ 2011-05-16 20:33 UTC (permalink / raw) To: Volker Armin Hemmann; +Cc: ReiserFS Development List On 05/16/2011 10:20 PM, Volker Armin Hemmann wrote: > On Monday 16 May 2011 22:16:11 you wrote: >> On 05/16/2011 09:55 PM, Volker Armin Hemmann wrote: >>> Hi, >>> >>> I have several r4 partitions, all with cryptcompress. >>> >>> I tried 2.6.38.x6 a few hours ago - after 3h I looked at dmesg and it >>> was >>> swamped with error messages and tracebacks. Sadly I tried to run fsck >>> before saving dmesg - and the box froze completely. >>> >>> I am now back to 2.6.36.4. fsck is running on one of the partitions. >>> Meanwhile I see tons of this: >>> >>> [ 153.379751] reiser4[kuiserver(2649)]: reiser4_inflate_cluster >>> (fs/reiser4/plugin/file/cryptcompress.c:1136)[edward-1460]: >>> [ 153.379756] WARNING: Inode 2975012: disk cluster 27 looks corrupted >>> [ 163.301372] reiser4[kuiserver(2669)]: dc_check_checksum >>> (fs/reiser4/plugin/file/cryptcompress.c:969)[edward-156]: >>> [ 163.301374] WARNING: Bad disk cluster checksum 799645291, (should be >>> 546616041) Fsck?-2) [...] >>> >>> known problem with 2.6.38.X? >> >> Yes, this is known and old problem. >> This is not specific to compression. > > ok, and how serious? Serious for what? Reiser4 in the current state is not suitable for production file servers. For home desktop - may be.. I am going to let fsck loose as soon as the first > partition is done. Should I prepare for some major cf? > I _can_ reproduce this problem. I don't need any extra-stuff. Thanks, Edward. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: reiser4+2.6.38.6 broken? 2011-05-16 20:33 ` Edward Shishkin @ 2011-05-16 21:12 ` Volker Armin Hemmann 2011-05-16 21:35 ` Edward Shishkin 0 siblings, 1 reply; 7+ messages in thread From: Volker Armin Hemmann @ 2011-05-16 21:12 UTC (permalink / raw) To: Edward Shishkin, reiserfs-devel On Monday 16 May 2011 22:33:06 you wrote: > On 05/16/2011 10:20 PM, Volker Armin Hemmann wrote: > > On Monday 16 May 2011 22:16:11 you wrote: > >> On 05/16/2011 09:55 PM, Volker Armin Hemmann wrote: > >>> Hi, > >>> > >>> I have several r4 partitions, all with cryptcompress. > >>> > >>> I tried 2.6.38.x6 a few hours ago - after 3h I looked at dmesg and > >>> it > >>> was > >>> swamped with error messages and tracebacks. Sadly I tried to run > >>> fsck > >>> before saving dmesg - and the box froze completely. > >>> > >>> I am now back to 2.6.36.4. fsck is running on one of the partitions. > >>> Meanwhile I see tons of this: > >>> > >>> [ 153.379751] reiser4[kuiserver(2649)]: reiser4_inflate_cluster > >>> (fs/reiser4/plugin/file/cryptcompress.c:1136)[edward-1460]: > >>> [ 153.379756] WARNING: Inode 2975012: disk cluster 27 looks > >>> corrupted > >>> [ 163.301372] reiser4[kuiserver(2669)]: dc_check_checksum > >>> (fs/reiser4/plugin/file/cryptcompress.c:969)[edward-156]: > >>> [ 163.301374] WARNING: Bad disk cluster checksum 799645291, (should > >>> be > >>> 546616041) Fsck?-2) > > [...] > > >>> known problem with 2.6.38.X? > >> > >> Yes, this is known and old problem. > >> This is not specific to compression. > > > > ok, and how serious? > > Serious for what? > Reiser4 in the current state is not suitable > for production file servers. For home desktop - > may be.. > > > I am going to let fsck loose as soon as the first > > > partition is done. Should I prepare for some major cf? > > I _can_ reproduce this problem. > I don't need any extra-stuff. and I don't expect you to. well, fsck worked. The partition was md1 - which means /var, which also houses portage tree on my setup and some other vital stuff. The first run with --build-fs failed with an 'unknown plugin id' error finishing with an 'operational error'. Secound run with --build-fs was successfull with only some files in lost+found. The important stuff seems to be there. R4 worked for me fine for a long time. But it seems like I should migrate the more important partitions away from it. How is reisefs doing at the moment? Glück Auf, Volker -- 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: reiser4+2.6.38.6 broken? 2011-05-16 21:12 ` Volker Armin Hemmann @ 2011-05-16 21:35 ` Edward Shishkin 2011-05-16 21:47 ` Volker Armin Hemmann 0 siblings, 1 reply; 7+ messages in thread From: Edward Shishkin @ 2011-05-16 21:35 UTC (permalink / raw) To: Volker Armin Hemmann; +Cc: reiserfs-devel On 05/16/2011 11:12 PM, Volker Armin Hemmann wrote: > On Monday 16 May 2011 22:33:06 you wrote: >> On 05/16/2011 10:20 PM, Volker Armin Hemmann wrote: >>> On Monday 16 May 2011 22:16:11 you wrote: >>>> On 05/16/2011 09:55 PM, Volker Armin Hemmann wrote: >>>>> Hi, >>>>> >>>>> I have several r4 partitions, all with cryptcompress. >>>>> >>>>> I tried 2.6.38.x6 a few hours ago - after 3h I looked at dmesg and >>>>> it >>>>> was >>>>> swamped with error messages and tracebacks. Sadly I tried to run >>>>> fsck >>>>> before saving dmesg - and the box froze completely. >>>>> >>>>> I am now back to 2.6.36.4. fsck is running on one of the partitions. >>>>> Meanwhile I see tons of this: >>>>> >>>>> [ 153.379751] reiser4[kuiserver(2649)]: reiser4_inflate_cluster >>>>> (fs/reiser4/plugin/file/cryptcompress.c:1136)[edward-1460]: >>>>> [ 153.379756] WARNING: Inode 2975012: disk cluster 27 looks >>>>> corrupted >>>>> [ 163.301372] reiser4[kuiserver(2669)]: dc_check_checksum >>>>> (fs/reiser4/plugin/file/cryptcompress.c:969)[edward-156]: >>>>> [ 163.301374] WARNING: Bad disk cluster checksum 799645291, (should >>>>> be >>>>> 546616041) Fsck?-2) >> >> [...] >> >>>>> known problem with 2.6.38.X? >>>> >>>> Yes, this is known and old problem. >>>> This is not specific to compression. >>> >>> ok, and how serious? >> >> Serious for what? >> Reiser4 in the current state is not suitable >> for production file servers. For home desktop - >> may be.. >> >> >> I am going to let fsck loose as soon as the first >> >>> partition is done. Should I prepare for some major cf? >> >> I _can_ reproduce this problem. >> I don't need any extra-stuff. > > and I don't expect you to. > > well, fsck worked. > > The partition was md1 - which means /var, which also houses portage tree on my > setup and some other vital stuff. > > The first run with --build-fs failed with an 'unknown plugin id' error > finishing with an 'operational error'. This looks like bug in fsck. Not related to the crash you have reported though.. > Secound run with --build-fs was successfull with only some files in > lost+found. The important stuff seems to be there. > > R4 worked for me fine for a long time. But it seems like I should migrate the > more important partitions away from it. I'll report as soon as I find the problem. Thanks, Edward. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: reiser4+2.6.38.6 broken? 2011-05-16 21:35 ` Edward Shishkin @ 2011-05-16 21:47 ` Volker Armin Hemmann 2011-05-16 21:57 ` Edward Shishkin 0 siblings, 1 reply; 7+ messages in thread From: Volker Armin Hemmann @ 2011-05-16 21:47 UTC (permalink / raw) To: Edward Shishkin, reiserfs-devel On Monday 16 May 2011 23:35:40 you wrote: > I'll report as soon as I find the problem. thank you very much. Until them I won't die using 2.6.36 ;) ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: reiser4+2.6.38.6 broken? 2011-05-16 21:47 ` Volker Armin Hemmann @ 2011-05-16 21:57 ` Edward Shishkin 0 siblings, 0 replies; 7+ messages in thread From: Edward Shishkin @ 2011-05-16 21:57 UTC (permalink / raw) To: Volker Armin Hemmann; +Cc: reiserfs-devel On 05/16/2011 11:47 PM, Volker Armin Hemmann wrote: > On Monday 16 May 2011 23:35:40 you wrote: > >> I'll report as soon as I find the problem. > > thank you very much. Until them I won't die using 2.6.36 ;) You will die in 2.6.36 with another workload. Edward. ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2011-05-16 21:57 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-05-16 19:55 reiser4+2.6.38.6 broken? Volker Armin Hemmann
2011-05-16 20:16 ` Edward Shishkin
[not found] ` <1725025.DC6atdjbiy@localhost>
2011-05-16 20:33 ` Edward Shishkin
2011-05-16 21:12 ` Volker Armin Hemmann
2011-05-16 21:35 ` Edward Shishkin
2011-05-16 21:47 ` Volker Armin Hemmann
2011-05-16 21:57 ` Edward Shishkin
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).