00:18:00onetruth quits [Remote host closed the connection]
00:18:19onetruth joins
00:27:22dbgft leaves
01:03:09<lunik1>sounds similar to snapraid
01:03:38<lunik1>if the drives are readonly how can the parity be updated? or will the data be static?
01:26:58aleph quits [Client Quit]
01:38:44aleph joins
01:48:13<Wayward>lunik1: well, i meant the volume mounted disks are write-once-read-many and configured to reject writes. the parity disk would similarly only need to be written to once, except when updated due to one of the drives receiving rare scheduled new writes.
01:49:09<Wayward>all of the disks can be USB enclosed and live on a bookshelf and be used independently, with the parity disk only needed in case of emergency or maintenance.
01:50:55<lunik1>so would the parity discs usually be live?
01:51:18<Wayward>bookshelf. fire safe. unimportant
01:51:49<Wayward>once every blue moon, you plug all your 15 USB drives (14 containing data, 1 containing parity) to perform validation
01:52:10<lunik1>snapraid sounds like an almost perfect fit, except it's generally intended to have all drives live
01:52:40<lunik1>but I think you could get away with just running a "degraded" array most of the time
01:52:59<Wayward>aye. all of the raid-like solutions seem to be intended for all disks spinning
01:53:26<lunik1>snapraid can access discs independently
01:53:26<Wayward>i just want a backup.exe that i casually launch from my start menu
01:54:02<lunik1>and has distinct parity discs, that it only writes to when updating the parity or restoring files
01:55:48<lunik1>and you control when that happens
01:56:21aleph quits [Client Quit]
02:08:47Wayward checking it out
02:09:45<Wayward><lunik1> snapraid sounds like an almost perfect fit, except it's generally intended to have all drives live
02:10:05<Wayward>snapraid website > To access a file, a single disk needs to spin, saving power and producing less noise.
02:10:57<lunik1>ah I meant live as in plugged in
02:11:20<Wayward>the software would complain if you dismounted unused volumes or drives?
02:12:03<Wayward>(the software wouldn't necessarily be called upon unless trouble strikes, anyway)
02:16:14<lunik1>if you don't use it it shouldn't be any the wiser, just as long as everything in place when you do use it
02:17:05<lunik1>I would avoid using the drive pooling feature if you intend to do that (and it's pretty basic, anyway)
02:19:43aleph joins
02:21:32<Wayward>also checking out their windows UI front end (side project)
02:24:48<Wayward>interesting too that it uses a file-based approach rather than a raw sector-based approach. suits me fine
02:24:56<lunik1>I have only used it on linux so I can't speak to the windows support
02:26:11<Wayward>file addressing can be less messy than sector addressing; fragmentation, unused sectors, etc
02:27:59<@JAA>You can find quite a lot of people using SnapRAID on /r/DataHoarder I believe if you're interested in looking for experience reports.
02:35:39<Wayward>++
02:50:39Lord_Nightmare quits [Quit: ZNC - http://znc.in]
02:53:17Lord_Nightmare (Lord_Nightmare) joins
03:20:49aleph quits [Client Quit]
03:22:18aleph joins
04:02:11qw3rty_ joins
04:05:53qw3rty__ quits [Ping timeout: 244 seconds]
04:06:53DogsRNice quits [Read error: Connection reset by peer]
04:59:14qw3rty__ joins
05:03:01qw3rty_ quits [Ping timeout: 252 seconds]
05:20:13etnguyen03 quits [Client Quit]
05:40:22BlueMaxima quits [Read error: Connection reset by peer]
07:03:59hooway joins
08:13:59sliccricc_ (sliccricc) joins
08:14:04sliccricc quits [Remote host closed the connection]
09:53:31sliccricc_ quits [Ping timeout: 264 seconds]
10:12:57sec^nd quits [Ping timeout: 240 seconds]
10:18:01sec^nd (second) joins
10:21:03rsn_ quits [Remote host closed the connection]
10:21:45rsn_ joins
10:22:34rsn_ quits [Remote host closed the connection]
10:22:46icedice joins
10:38:14Ryz quits [Remote host closed the connection]
10:39:04Ryz (Ryz) joins
11:05:19Arcorann_ joins
11:06:27Arcorann quits [Ping timeout: 244 seconds]
11:22:42Arcorann__ joins
11:25:25Arcorann_ quits [Ping timeout: 240 seconds]
11:37:27Arcorann__ quits [Ping timeout: 244 seconds]
12:33:43lunik1 quits [Quit: Ping timeout (120 seconds)]
12:34:02lunik1 joins
12:44:53kpcyrd quits [Quit: kpcyrd]
12:45:05kpcyrd (kpcyrd) joins
13:15:37daalekz quits [Ping timeout: 244 seconds]
13:19:28yano quits [Quit: WeeChat, The Better IRC Client, https://weechat.org/]
13:21:33yanome (yano) joins
13:22:32yano (yano) joins
13:26:23tech234a quits [Read error: Connection reset by peer]
13:26:24@jrwr quits [Read error: Connection reset by peer]
13:26:34aarchi quits [Read error: No route to host]
13:26:36janpaul123 quits [Read error: Connection reset by peer]
13:26:36@EggplantN2 quits [Read error: Connection reset by peer]
13:26:36mgrandi quits [Read error: Connection reset by peer]
13:27:13space quits [Read error: Connection reset by peer]
13:28:04mgrandi (mgrandi) joins
13:28:06janpaul123 (janpaul123) joins
13:28:14jrwr (jrwr) joins
13:28:14@ChanServ sets mode: +o jrwr
13:28:30EggplantN2 joins
13:28:41tech234a (tech234a) joins
13:29:45space (space) joins
13:30:57aarchi (aarchi) joins
13:32:43EggplantN2 quits [Changing host]
13:32:43EggplantN2 (EggplantN) joins
13:32:44@ChanServ sets mode: +o EggplantN2
13:58:31etnguyen03 (etnguyen03) joins
14:18:33onetruth quits [Remote host closed the connection]
14:18:54onetruth joins
14:38:56sliccricc_ (sliccricc) joins
14:41:47sliccricc_ quits [Remote host closed the connection]
14:42:13sliccricc_ (sliccricc) joins
14:50:32benjinsmith joins
14:52:56benjins quits [Ping timeout: 265 seconds]
15:03:05benjinsmith is now known as benjins
15:30:59ThreeHeadedMonkey quits [Ping timeout: 244 seconds]
15:32:28ThreeHeadedMonkey (ThreeHeadedMonkey) joins
15:46:14sliccricc_ quits [Remote host closed the connection]
15:52:43justaguy is now known as AltroskyAS207616_Mystique
15:55:03<atphoenix>Wayward, also look at DrivePool and DriveBender. They automate file-level mirroring. across independent disks. They work best for data that is mostly read-only.
15:58:04sliccricc (sliccricc) joins
15:58:39sliccricc quits [Remote host closed the connection]
15:58:54sliccricc (sliccricc) joins
16:12:07LeGoupil joins
16:16:54LeGoupil quits [Client Quit]
16:50:09rsn joins
17:34:59lennier2 joins
17:37:37lennier1 quits [Ping timeout: 252 seconds]
17:37:40lennier2 is now known as lennier1
17:51:29onetruth quits [Read error: Connection reset by peer]
18:25:35space quits [Read error: Connection reset by peer]
18:25:42space (space) joins
18:25:45mgrandi quits [Read error: Connection reset by peer]
18:25:57mgrandi (mgrandi) joins
18:50:00benjinsmith joins
18:52:11benjins quits [Ping timeout: 265 seconds]
18:52:14benjinsmith is now known as benjins
19:38:59DLoader quits [Ping timeout: 244 seconds]
19:47:09britmob quits [Read error: Connection reset by peer]
19:48:06britmob joins
19:50:14sliccricc quits [Remote host closed the connection]
19:50:31sliccricc (sliccricc) joins
19:57:12DLoader joins
20:16:04Church joins
20:16:04aleph quits [Read error: Connection reset by peer]
20:43:55sliccricc quits [Ping timeout: 264 seconds]
21:28:50<Wayward>atphoenix, thanks, I will. Sounds like the pitch SnapRAID gives, but I didn't see those two mentioned on their competition comparison chart.
21:31:15<Wayward>But who are we kidding, really. Most of our archiving is write-only; never to be read. :P
21:32:35britmob quits [Read error: Connection reset by peer]
21:41:29<Wayward>hmm, both a bit pricy licensing.
21:44:55britmob joins
21:51:37<@kiska>mgrandi: wanna see some wonderful asp.net slides? https://server8.kiska.pw/uploads/0e0ddd80cba50dcc/image.png
22:22:01daalekz (daalekz) joins
22:27:39daalekz quits [Client Quit]
22:44:32mutantmonkey quits [Remote host closed the connection]
22:44:58mutantmonkey (mutantmonkey) joins
23:04:03BlueMaxima joins
23:04:26@jrwr quits [Read error: Connection reset by peer]
23:04:26janpaul123 quits [Read error: Connection reset by peer]
23:04:35janpaul123 (janpaul123) joins
23:04:57jrwr (jrwr) joins
23:04:57@ChanServ sets mode: +o jrwr
23:18:34treora quits [Ping timeout: 244 seconds]
23:28:41treora joins
23:43:44<mgrandi>Heh, I've only used it for API stuff, I assume those are for some auto generated view thing
23:51:40@kiska quits [Quit: Ping timeout (120 seconds)]
23:53:30kiska (kiska) joins
23:53:30@ChanServ sets mode: +o kiska