I've had similar errors on a Linux server, random filesystem corruption, damaged files and directories. The problem manifests itself only with the high disk activity, such as running pretty loaded squid cache. It seems what I was right suspecting bad motherboard (VIA 82C586-something, Celeron Slot 1). Turning off PIO, UDMA (it has fairly new IDE drive) and UDMA support in kernel seems to help. No problems so far, 20+ days uptime (it was no more than a week before). Squid cache directory was damaged every time. The kernel is 2.2.13, but I don't think filesystem corruption is kernel related in my case. Never, never buy cheap motherboard for a server and actively protest even if your boss tells you about limited budget. Bad hardware could be a whole can of worms. I hope I will get this bad motherboard replaced soon. Of course I can't reproduce the problem with Windows 95, high server load needed for the problem manifests itself. Sad story...
They don't allow ssh in because of its ability to forward ports (they don't want 30 people to run X from one machine at time). I told him what this feature can be disabled by compile-time option (maybe in config file too). So maybe there will be ssh access soon.
The accounts have to be deleted after 30 days to clean up id space. Linux uid_t is only unsigned short (on nis server). But if I drop him an email, he will be able to restore my account.
Are you updating your NT server with SP without reboot? Service Packs released with less than a year period between them. How can you keep your NT up continuously for a year still following service packs?
What have you been done to track the reason for Linux instability. To have server crashing every 5 days is a bit annoying IMHO, so you'd have something to be done with it. Many people said what Linux is stable for them, so maybe it is the problem with your setup?
FreeBSD has its problems too. Read the freebsd-stable mailing list and see what kind of problems FreeBSD users have. There is no perfect OS!
No, I think we cound call it a normal PC. I don't remember where I got it, but I saw it has ISA and PCI slots and they used fairly standard hardware. Then they start to ship it we'll know for sure.
As a man who lived in communism (or socialism, whatever you call it) I can tell you what you are plain wrong. GNU has nothing in common with communism, RMS just wanted to give us freedom. So it is more democratic. Plese, don't start flamewar/talk about politics here. The topic is iToaster, remember this.
How much times a day you wait your mac booting? I only have to (re)boot my Linux PC at home (486!) around once a week. Our server at university boots long time, but reboots are rare and planned, so I don't care. How long it boots is not an issue here, you see.
Slashdot Mirror
I've had similar errors on a Linux server, random filesystem corruption, damaged files and directories. The problem manifests itself only with the high disk activity, such as running pretty loaded squid cache. It seems what I was right suspecting bad motherboard (VIA 82C586-something, Celeron Slot 1). Turning off PIO, UDMA (it has fairly new IDE drive) and UDMA support in kernel seems to help. No problems so far, 20+ days uptime (it was no more than a week before). Squid cache directory was damaged every time. The kernel is 2.2.13, but I don't think filesystem corruption is kernel related in my case. Never, never buy cheap motherboard for a server and actively protest even if your boss tells you about limited budget. Bad hardware could be a whole can of worms. I hope I will get this bad motherboard replaced soon. Of course I can't reproduce the problem with Windows 95, high server load needed for the problem manifests itself. Sad story...
Talked to root too and got some additional info:
Are you updating your NT server with SP without reboot? Service Packs released with less than a year period between them. How can you keep your NT up continuously for a year still following service packs?
What have you been done to track the reason for Linux instability. To have server crashing every 5 days is a bit annoying IMHO, so you'd have something to be done with it. Many people said what Linux is stable for them, so maybe it is the problem with your setup?
FreeBSD has its problems too. Read the freebsd-stable mailing list and see what kind of problems FreeBSD users have. There is no perfect OS!
No, I think we cound call it a normal PC. I don't remember where I got it, but I saw it has ISA and PCI slots and they used fairly standard hardware. Then they start to ship it we'll know for sure.
As a man who lived in communism (or socialism, whatever you call it) I can tell you what you are plain wrong. GNU has nothing in common with communism, RMS just wanted to give us freedom. So it is more democratic. Plese, don't start flamewar/talk about politics here. The topic is iToaster, remember this.
How much times a day you wait your mac booting?
I only have to (re)boot my Linux PC at home (486!) around once
a week. Our server at university boots long time,
but reboots are rare and planned, so I don't care.
How long it boots is not an issue here, you see.