Am i the only one that has problems in file corruptions on haiku?
Since i installed Haiku on my netbook acer (ssd drive) sometimes files get damaged, dunno why… dunno if it’s related to the sync command from terminal or other, but i often find some (once upon a time) working archive broken…
this night i coded for hours and hours, then i put my netbook away (still open) and I contunued this morning. The program i was coding worked well this morning…
I saved all the work, I closed all the programs manually, then I shutted down the machine.
After some minutes (like a drug) I started again the machine, i started my program and i got strange errors; I opened the source code (python)
and… Voilà system error messages like these:
2238882825]
KERN: [net/atheroswifi/0] scan_task: chan 12g -> 1g [active, dwell min 20ms max 0ms]
KERN: [net/atheroswifi/0] ieee80211_ref_node (ieee80211_send_probereq:1644) 0x84395000<00:22:69:20:f6:f6> refcnt 3
KERN: [net/atheroswifi/0] scan_task: chan 1g -> 6g [active, dwell min 20ms max 0ms]
KERN: [net/atheroswifi/0] ieee80211_ref_node (ieee80211_send_probereq:1644) 0x84395000<00:22:69:20:f6:f6> refcnt 3
KERN: [net/atheroswifi/0] scan_task: chan 6g -> 11g [active, dwell min 20ms max 0ms]
KERN: [net/atheroswifi/0] ieee80211_ref_node (ieee80211_send_probereq:1644) 0x84395000<00:22:69:20:f6:f6> refcnt 3
KERN: [net/atheroswifi/0] scan_task: chan 11g -> 7g [active, dwell min 20ms max 0ms]
KERN: [net/atheroswifi/0] ieee80211_ref_node (ieee80211_send_probereq:1644) 0x84395000<00:22:69:20:f6:f6> refcnt 3
KERN: [net/atheroswifi/0] scan_task: chan 7g -> 13g [active, dwell min 20ms max 0ms]
KERN: [net/atheroswifi/0] iee = task.due
and some pieces of code erased
bad indentations
and so on…
so it seems that some random syslog has saved to my file!!! and maybe it’s the same happened to the compressed archives that i lost
Are those from your syslog? They appear to relate to WiFi. Maybe you missed the real drive errors?
Very important: run checkfs to see if your filesystem is corrupt or not and to fix any errors. Take note of the output info.
You should file a ticket yourself with your syslog. Could be your hardware setup that is causing this. Could also be the sync command because most people do not use that.
i run checkfs the first time it gave me this output:
29148 nodes checked,
0 blocks not allocated,
0 blocks already set,
205 blocks could be freed
files 27199
directories 1754
attributes 109
attr. dirs 77
indices 9
later the 205 blocks gone and became 0
anyway, yes these errors appears in syslog , or better syslog is made by only those errors:
actually my atheros wifi isn’t in use cause i use ethernet
but when i use the wifi adapter it works well, maybe those errors are written cause the wifi is in continous search of an accesspoint
but this does not explain why those errors were written in my file, i’m suspicious about sync cause the only reasonable way to write those things in a wrong position is that while he had to write in syslog maybe a sync forced to write somewhere else, (and cause it happens only in the same period (not the exact time) of usage of sync), I hope to not say an abomination but maybe sync make interference with the haiku syncing at the moment of shutdown…
checkfs tries and usually can fix filesystem corruption. It fixed the filesystem errors above but some of your files maybe damaged.
yes, file a ticket with syslog so developer can have better look. Also let them know about sync. They maybe better able to help.
A little test: #1 you should try booting and shutting down Haiku after 5 minutes or longer. Do this couple of times. #2 run checkfs to see if filesystem Ok or corrupted. If Ok, then do #3. #3 run sync couple of different times #4 run checkfs to see if filesystem Ok or corrupted.
This hopefully narrows down what is causing the problem. Syslog may have more information about it.
[quote]0 blocks not allocated,
0 blocks already set,
0 blocks could be freed[/quote]
All of these should be zero if filesystem checks out Ok. If not zero then filesystem became messed up for some reason.
“could be freed” would probably be clearer as “were freed”, many Haiku developers are not native English speakers. So you should not expect to see the same number next time.
Axel Dörfler wrote an explanation of the main thing checkbfs does in Haiku