Earlier quoted context omitted.
A few years ago I finally bought a USB drive to read an old 3.5" floppy from the late '90s on which I had archived my e-mail messages before moving away to college. I completely forgot about write protection (as well as atime write-backs). I managed to read a surprising amount of data off of the disk, but I think less than if I had remembered to write-protect the disk before inserting it into the drive. The files wer…
So rare to see ppl writing about sync. sync;sync;halt was once a legit way to shut down ;)
I'm hosting a website on a RAID0 of 30 floppy drives
101–110 of 161 posts
Re: I'm hosting a website on a RAID0 of 30 floppy drives
#102Earlier quoted context omitted.
So rare to see ppl writing about sync. sync;sync;halt was once a legit way to shut down ;)
Or maybe three times sync;sync;sync just to make sure :)
Re: I'm hosting a website on a RAID0 of 30 floppy drives
#103Site seems to be really slow currently.
Re: I'm hosting a website on a RAID0 of 30 floppy drives
#104project is awesome. Also- Tell me you're into Chiodos without telling me you're into Chiodos. Big ol dose of nostalgia listening to your old metalcore tracks.
Re: I'm hosting a website on a RAID0 of 30 floppy drives
#105Earlier quoted context omitted.
On top of the block layer cache there's also the namei cache for filename to inode lookups, I'm not sure if that covers a file not found case or just a success path, but it may apply here too.
Yep, that's called a "negative dentry".
The DDoS scenario would be doing GET requests of random nonexistent filenames. You could change the name at every step so that the check for a negative dentry is never a cache hit.
Re: I'm hosting a website on a RAID0 of 30 floppy drives
#106Earlier quoted context omitted.
No. The cache is at the block layer, not the file/directory layer. So the filesystem will look up the directory structure, which will be cached.
Actually, no. There is no general block layer cache - the closest thing is the page cache, which is at the file level.
Re: I'm hosting a website on a RAID0 of 30 floppy drives
#107Earlier quoted context omitted.
> RAID0 is for speed only In this case, the theoretical maximum bandwidth is 24M Bit /s. The problem is the old, slow usb bottleneck. I'm not sure how much faster, probably hundreds of bps rather than under 24, but a faster RAID0 rig would be to instead have 30x Mac G4 Digital Audios connected via gigabit switch, and share then RAID0 the internal floppies. It would also have whatever advantage running an XGrid PPC cl…
I don't know about that BW claim. Back when mp3 was new and computers usually had floppy drives I did the obvious and mp3 bitrates above 64K or so tended to stutter and significantly below 64K did not stutter. Something like voice encoded at 32K sounded at least as good as a phone and played back off a 1.44 floppy and IIRC that was about the best that could be done. You will probably be surprised how long an audio re…
He got results ranging from 25 KB/s - 100 KB/s
Re: I'm hosting a website on a RAID0 of 30 floppy drives
#108> Server uptime: 20 seconds
> Server load: 157.41 158.15 155.66
oh
Re: I'm hosting a website on a RAID0 of 30 floppy drives
#109I'd expect the vast majority of IO requests to be served from the kernel's IO cache (we're talking 30 * 1.44MBs here so just under 50MB, trivial for even an old computer to hold in RAM), thus I wouldn't be surprised for it to be very fast and reliable as long as he sticks to read-only workloads - those would never actually touch the floppies beyond the initial read.
I did watch -n 1 'sync; echo 3 > /proc/sys/vm/drop_caches' to try and get around it. I think it's working, because boy is it noisy lol