Opened 15 years ago
Closed 6 years ago
#4950 closed bug (fixed)
KDL as soon as Deskbar and desktop appear
Reported by: | Kev | Owned by: | nobody |
---|---|---|---|
Priority: | high | Milestone: | R1 |
Component: | File Systems/BFS | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
I'm not sure if this is related, but something strange happened during my last successful boot on my Haiku partition. I sent an e-mail like normal, just a reply, no attachments. Then, every time the mail daemon would check for mail (every x minutes or when I used the context menu on the replicant) it would bring up the status bar sending an e-mail, and send it again. (Well, I haven't heard back yet, but I'm tentatively assuming it's the last one that it was sending repeatedly.)
Then, I noticed that even though I'd read all my messages, the replicant context menu always said that I had one new message. I opened the query, and tried a few times to mark the message as read, both by opening the e-mail and using the close->leave as read, and right clicking the item in the query results and choosing mark as read. Nothing made it go away, so I thought I'd reboot.
Now, every time I reboot, a split second after the Deskbar and desktop show up, I'm KDL'd. I can't remember the error message so I'll have to update later with that, but anyway, I'm on haiku-nightly-hrev33859-x86gcc2hybrid and hadn't had any problems, using it every day since the day that one was released.
Attachments (1)
Change History (17)
by , 15 years ago
comment:1 by , 15 years ago
comment:3 by , 15 years ago
That common_read_link line is the one I was replying to (or maybe it's my reply, since, it was actually a forward and it doesn't say that on that line either. Anyway, same thread.)
comment:4 by , 15 years ago
Component: | System/Kernel → File Systems/BFS |
---|---|
Version: | R1/alpha1 → R1/Development |
Please add images as attachments instead of putting it somewhere else.
comment:5 by , 15 years ago
BTW, I forgot to mention I ran chkbfs on each of my partitions from BeOS and none of them reported errors.
Re: attachments, I couldn't seem to get the file small enough for the limits imposed while still being able to read the text in it. So that was the only way I could think of to do it. Besides...less burden on your servers, right?
If there's nothing else I can try, I'd like to upgrade to the latest nightly so there's a chance I can be using Haiku again...please advise...
comment:6 by , 15 years ago
R5's chkbfs really doesn't check/fix all that much except block allocation mismatches, it can't/won't try to handle more complex problems...if you can boot a Haiku Live CD you could try running checkfs on the Haiku partitions from there though.
comment:7 by , 15 years ago
Unfortunately, I don't have one. Is there anything I can do on bootup or from R5, or should I just upgrade?
comment:8 by , 15 years ago
This seems to be just a bug in BFS (with long symlinks) - this won't go away by running checkfs, I'm afraid :-)
comment:9 by , 12 years ago
Do you still have this issue or can we assume that this has been fixed in the past 3 years?
comment:10 by , 12 years ago
I haven't been using Haiku for e-mail since I had some data loss issues a few years ago. And also kind of left IT for a while. Since then I've written over my Haiku system with Alpha 4.1, so after doing that I'm not sure how to try to reproduce it. Maybe Axel can comment having had a better idea of what the bug actually was?
comment:11 by , 12 years ago
I've pretty much forgotten about this one. Since I also have no recollection of having fixed it, let's just keep the ticket open for now.
comment:12 by , 12 years ago
Unfortunately I can't test it now, since Gmail POP access is currently unsupported by Haiku. But if/when that works again I'll give it a shot.
comment:13 by , 8 years ago
Do you still have that image by any chance? I'd like to look into it, but it's hard without actually seeing the KDL (that's why I asked for an attachment; not that I knew that it would take forever until I would look at it).
comment:14 by , 8 years ago
It might actually be a duplicate of #5282, in which case it would have been fixed in the mean time.
comment:15 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:16 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Presuming fixed, then. Please open a new ticket if it's still around.
It's not completely outside the realm of possibility that you have filesystem corruption going on, but without the panic message and backtrace there really isn't much to go off here.