Skip to contentSkip to conversation

2.6.0-test2: cursor started to disappear

DISCUSSION Pavel Machek 5 participants 11 messages Jul 28, 2003 – Jul 29, 2003

lore
Share & tools
lore
#0 lore raw

Hi!

Under 2.6.0-test2 cursor problems got worse... Sometimes cursor just disappears. Switching consoles does not help.

Plus I'm seeing some silent data corruption. It may be swsusp or loop related, don't yet know how to reproduce it (ext2 on hp omnibook xe3).
Pavel

Signature · 2 lines
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
#1 lore raw
Quoted 2 lines · Pavel Machek

Plus I'm seeing some silent data corruption. It may be swsusp or loop related

Loop is not stable at all. Unsuitable for daily use.

#2 lore raw

Hi!

Quoted 4 lines
Quoted 2 lines

Plus I'm seeing some silent data corruption. It may be swsusp or loop related

Loop is not stable at all. Unsuitable for daily use.

Ouch... I have my most important filesystem on loop. Time to go back to 2.4.X? Or do you have some patches you want me to try?

Pavel

Signature · 2 lines
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
#3 lore raw
Quoted 7 lines · Pavel Machek
Quoted 4 lines
Quoted 2 lines

Plus I'm seeing some silent data corruption. It may be swsusp or loop related

Loop is not stable at all. Unsuitable for daily use.

Ouch... I have my most important filesystem on loop. Time to go back to 2.4.X? Or do you have some patches you want me to try?

[maybe an extra backup?]

Jari's version of loop.c has always been solid.

#4 lore raw

Hi!

Quoted 9 lines
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines

Plus I'm seeing some silent data corruption. It may be swsusp or loop related

Loop is not stable at all. Unsuitable for daily use.

Ouch... I have my most important filesystem on loop. Time to go back to 2.4.X? Or do you have some patches you want me to try?

[maybe an extra backup?]

Hmm, looks like I should do that.

Quoted 1 line

Jari's version of loop.c has always been solid.

Jari Ruusu? Okay, I'll test that.

Pavel

Signature · 2 lines
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
#5 lore raw
In reply to Pavel Machek
Quoted 9 lines · Pavel Machek

Hi!

Quoted 4 lines
Quoted 2 lines

Plus I'm seeing some silent data corruption. It may be swsusp or loop related

Loop is not stable at all. Unsuitable for daily use.

Ouch... I have my most important filesystem on loop. Time to go back to 2.4.X? Or do you have some patches you want me to try?

Time to go back to 2.0.x --- it's the only kernel where loop was correctly (almost) deadlockless implemented :)

Mikulas

#6 lore raw
In reply to Andries Brouwer
Quoted 7 lines · Andries Brouwer
Quoted 2 lines · Pavel Machek

Plus I'm seeing some silent data corruption. It may be swsusp or loop related

Loop is not stable at all. Unsuitable for daily use.

That's the first I've heard about it. Do you have some details on this? A test case perhaps?

#7 lore raw
Quoted 11 lines · Andrew Morton
Quoted 7 lines · Andries Brouwer
Quoted 2 lines · Pavel Machek

Plus I'm seeing some silent data corruption. It may be swsusp or loop related

Loop is not stable at all. Unsuitable for daily use.

That's the first I've heard about it. Do you have some details on this? A test case perhaps?

Yes, there are many reports, and it is easy to confirm.

By some coincidence just a moment ago we saw the announcement of Bugzilla bug 1000:

[Bug 1000] New: file corruption using cryptoloop on ext2/ext3

Andries

#8 lore raw
Quoted 14 lines · Andries Brouwer
Quoted 11 lines · Andrew Morton
Quoted 7 lines · Andries Brouwer
Quoted 2 lines · Pavel Machek

Plus I'm seeing some silent data corruption. It may be swsusp or loop related

Loop is not stable at all. Unsuitable for daily use.

That's the first I've heard about it. Do you have some details on this? A test case perhaps?

Quoted 6 lines

Yes, there are many reports, and it is easy to confirm.

By some coincidence just a moment ago we saw the announcement of Bugzilla bug 1000:

[Bug 1000] New: file corruption using cryptoloop on ext2/ext3

That's cryptoloop. I thought you were referring to vanilla loop.

Are you saying that the problems are only with cryptoloop, or does normal old loop have some bug?

#9 lore raw
Quoted 4 lines · Andrew Morton

That's cryptoloop. I thought you were referring to vanilla loop.

Are you saying that the problems are only with cryptoloop, or does normal old loop have some bug?

It would be too optimistic to claim that it has none, but the easily provoked corruption I mentioned is for cryptoloop. Sorry for being imprecise.

#10 lore raw
In reply to Andrew Morton

Hi!

Quoted 7 lines
Quoted 4 lines
Quoted 2 lines

Plus I'm seeing some silent data corruption. It may be swsusp or loop related

Loop is not stable at all. Unsuitable for daily use.

That's the first I've heard about it. Do you have some details on this? A test case perhaps?

After a while (week of use), kernel started complaining about "block already freed in inode X" or something like that. I rebooted and fsck found nothing serious (that is normal loop). I've now switched to Jari's version of loop -- I'd like to keep this filesystem.

Pavel

Signature · 2 lines
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]