https://dev.arvados.org/https://dev.arvados.org/favicon.ico?15576888422016-01-07T14:22:36ZArvadosArvados - Bug #8148: [FUSE] When we give up trying to write a block, the next operation on the file should failhttps://dev.arvados.org/issues/8148?journal_id=340402016-01-07T14:22:36ZBryan Coscabcosca@curii.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/34040/diff?detail_id=33440">diff</a>)</li></ul> Arvados - Bug #8148: [FUSE] When we give up trying to write a block, the next operation on the file should failhttps://dev.arvados.org/issues/8148?journal_id=340422016-01-07T14:30:34ZBrett Smithbrett.smith@curii.com
<ul></ul><p>These services are reporting 503 because they're full. We recently added some space by adding a keep5.wx5k7, on the 6th. So the question is, why didn't this job see that?</p> Arvados - Bug #8148: [FUSE] When we give up trying to write a block, the next operation on the file should failhttps://dev.arvados.org/issues/8148?journal_id=340432016-01-07T14:35:57ZBrett Smithbrett.smith@curii.com
<ul></ul><p>The job, and therefore its FUSE mount, started before we added keep5.wx7k5. Writing these blocks likely failed because it tried to write them before keep5.wx7k5 was available.</p>
<p>Bryan, this job is safe to restart immediately. The bug here is probably that FUSE needs to refresh the Keep service list and retry with new services to account for cases like this.</p> Arvados - Bug #8148: [FUSE] When we give up trying to write a block, the next operation on the file should failhttps://dev.arvados.org/issues/8148?journal_id=340442016-01-07T14:45:05ZBrett Smithbrett.smith@curii.com
<ul><li><strong>Subject</strong> changed from <i>keep1 keep2 keep3 503 error</i> to <i>[FUSE] When writing a block fails, keep retrying over the life of the process</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/34044/diff?detail_id=33442">diff</a>)</li></ul> Arvados - Bug #8148: [FUSE] When we give up trying to write a block, the next operation on the file should failhttps://dev.arvados.org/issues/8148?journal_id=345222016-01-20T18:24:23ZBrett Smithbrett.smith@curii.com
<ul><li><strong>Target version</strong> set to <i>Arvados Future Sprints</i></li></ul> Arvados - Bug #8148: [FUSE] When we give up trying to write a block, the next operation on the file should failhttps://dev.arvados.org/issues/8148?journal_id=368472016-03-22T18:38:58ZBrett Smithbrett.smith@curii.com
<ul><li><strong>Subject</strong> changed from <i>[FUSE] When writing a block fails, keep retrying over the life of the process</i> to <i>[FUSE] When we give up trying to write a block, the next operation on the file should fail</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/36847/diff?detail_id=36064">diff</a>)</li></ul> Arvados - Bug #8148: [FUSE] When we give up trying to write a block, the next operation on the file should failhttps://dev.arvados.org/issues/8148?journal_id=948792021-07-07T18:27:44ZWard Vandewegeward@curii.com
<ul><li><strong>Target version</strong> deleted (<del><i>Arvados Future Sprints</i></del>)</li></ul> Arvados - Bug #8148: [FUSE] When we give up trying to write a block, the next operation on the file should failhttps://dev.arvados.org/issues/8148?journal_id=1121342023-02-14T22:24:02ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Release</strong> set to <i>60</i></li></ul> Arvados - Bug #8148: [FUSE] When we give up trying to write a block, the next operation on the file should failhttps://dev.arvados.org/issues/8148?journal_id=1234982024-03-01T21:14:20ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Target version</strong> set to <i>Future</i></li></ul>