| Time |
Nickname |
Message |
|
01:31
🔗
|
iabak-reg |
03registrar 05master d1297ac 06other 10SHARD3/pubkeys registration of robertsdavidddr on SHARD3 |
|
07:56
🔗
|
|
db48x`` is now known as db48x |
|
10:14
🔗
|
|
VADemon_ has joined #internetarchive.bak |
|
10:16
🔗
|
|
VADemon has quit IRC (Ping timeout: 255 seconds) |
|
11:43
🔗
|
|
zino has quit IRC (Remote host closed the connection) |
|
13:05
🔗
|
|
jadz has quit IRC (Read error: Operation timed out) |
|
13:45
🔗
|
|
zino has joined #internetarchive.bak |
|
15:20
🔗
|
|
jadz has joined #internetarchive.bak |
|
15:24
🔗
|
|
VADemon_ has quit IRC (Ping timeout: 370 seconds) |
|
15:47
🔗
|
iabak-reg |
03registrar 05master 7f9a334 06other 10SHARD11/pubkeys registration of naclosagc on SHARD11 |
|
15:47
🔗
|
iabak-reg |
03registrar 05master ee8284f 06other 10SHARD10/pubkeys registration of naclosagc on SHARD10 |
|
17:10
🔗
|
|
zino has quit IRC (Read error: Connection reset by peer) |
|
18:48
🔗
|
|
VADemon has joined #internetarchive.bak |
|
21:11
🔗
|
|
xperia64 has joined #internetarchive.bak |
|
21:16
🔗
|
xperia64 |
I'm not sure if the cronjob is working as intended on my setup |
|
21:29
🔗
|
xperia64 |
I am one of the larger backups on the list that is set to expire this week. The backups are still intact, but my storage is so slow I'm not sure it will fsck by then |
|
22:13
🔗
|
|
zino has joined #internetarchive.bak |
|
22:37
🔗
|
db48x |
xperia64: hmm. does the fsck need to be run more often, or broken up into smaller stages, or what? |
|
22:47
🔗
|
xperia64 |
I'm not exactly sure. I can't download new shards because the storage essentially full. I'd like to do the entire fsck all at once every two months |
|
22:48
🔗
|
xperia64 |
Also, I've noticed a lot of "iabak-hourlysync" processes that haven't been exiting, some of which have been running since the end of february |
|
22:49
🔗
|
db48x |
hmm |
|
22:49
🔗
|
db48x |
well, you can kill the iabak-hourlysync processes if you like |
|
22:50
🔗
|
db48x |
although if they were really syncing all your repositories once per hour, then you wouldn't be in danger of being expired |
|
22:51
🔗
|
db48x |
xperia64: if you run a "git annex sync" manually in the shard or shards that are about to expire, that will help |
|
22:56
🔗
|
xperia64 |
permission denied (publickey) when running manually |
|
22:57
🔗
|
xperia64 |
nevermind, got it. |
|
23:04
🔗
|
xperia64 |
The fact that my setup has actually worked for this long is pretty amazing. 48 drives: 42 iSCSI, 6 SATA, btrfs RAID 10. Recently upgraded from a core2duo with 6GB of RAM to a Phenom x4 with 8GB |
|
23:43
🔗
|
db48x |
:) |
|
23:48
🔗
|
db48x |
xperia64: when was the last time you ran iabak? |
|
23:51
🔗
|
xperia64 |
I started it last night, and I believe it was fscking all night. |
|
23:52
🔗
|
db48x |
and when was the last time the cronjob/systemd service ran? |
|
23:53
🔗
|
xperia64 |
The last one I saw in the output of ps was from a few days ago |