Difference between revisions of "Guerilla filesystem"
From Makers Local 256
(→Pros: minor addition of humor) |
m (Added section for my notes) |
||
Line 24: | Line 24: | ||
** Might have to be limited to unimportant/temporary data. | ** Might have to be limited to unimportant/temporary data. | ||
* Potentially not very mobile. | * Potentially not very mobile. | ||
+ | |||
+ | ==Brimstone's Notes== |
Revision as of 15:58, 26 January 2007
Contents
[hide]Overview
A script or app that auto-searches for writeable space of any type, mounts them using FUSE or something similar, and then RAIDs them all together potentially creating vast amounts of storage seemingly out of the ether.
Notes
- JBOD with some sort of external parity would be ideal, but RAID 5+0 would work as well.
- The need for parity is imperative because since you don't own the space you never know when a part might disappear and need to be replaced.
- It will definitely need to group found space based on size for optimal use in different RAID arrays.
- Might need to keep a list of backup space for quick and easy replacement.
- I have no idea how long it would take to calculate parity across all of that, but that would need to be determined to weigh feasibility.
- Could sniff network traffic to find available space rather than actively scanning for it.
Pros
- Potentially limitless storage that you didn't even know existed at your disposal.
- It's free!
- Plausible deniability for questionable content.
- "It's not my hardware sir, I don't know what it was doing mounted..."
- "No sir, I don't know where it's located..."
- "It's not my hardware sir, I don't know what it was doing mounted..."
- Christmas everytime you df -k!
- You never know how much it'll find from day to day.
Cons
- While there is parity, it could take a long time to rebuild.
- May or may not support multiple volume failures.
- Might have to be limited to unimportant/temporary data.
- Potentially not very mobile.