[tahoe-lafs-trac-stream] [Tahoe-LAFS] #4176: Trac regularly unavailable with no space left on device

[Tahoe-LAFS]

#4176: Trac regularly unavailable with no space left on device
------------------------------------+-----------------------
     Reporter:  btlogy              |      Owner:  meejah
         Type:  defect              |     Status:  new
     Priority:  normal              |  Milestone:  undecided
    Component:  dev-infrastructure  |    Version:  n/a
   Resolution:                      |   Keywords:
Launchpad Bug:                      |
------------------------------------+-----------------------
Description changed by btlogy:

Old description:

> This unavailability has been observed already a few time before (at least
> since #4095 last year), but seems to happen on daily basis since a few
> last weeks (end of March 2025).
>
> See this list of past [https://github.com/tahoe-lafs/infrastructure-
> upptime/issues?q=is%3Aissue%20state%3Aclosed%20Tickets incidents].
>
> The error show by the Trac software seems to be explicit:
>
> {{{
> IOError: [Errno 28] No space left on device
> }}}
>
> In addition to the service being often unavailable (to create and manage
> this issue for instance), one could be concerned of the increased risk
> data of corruption.
>
> Meejah has been made aware of this problem on IRC and will hopefully be
> able to at least free some disk space (maybe 18th or 19th of May).
>
> But 2 questions remains:
> - could the root cause be identified to increase the availability and
> reduce the risk of corruption?
> - is there a backup to restore the data in case those would end been
> corrupted?

New description:

 This unavailability has been observed already a few time before (at least
 since #4095 last year), but seems to happen on daily basis since a few
 last weeks (end of March 2025).

 See this list of past [https://github.com/tahoe-lafs/infrastructure-
 upptime/issues?q=is%3Aissue%20state%3Aclosed%20Tickets incidents].

 The error show by the Trac software seems to be explicit:

 {{{
 IOError: [Errno 28] No space left on device
 }}}

 In addition to the service being often unavailable (to create and manage
 this issue for instance), one could be concerned of the increased risk
 data of corruption.

 Meejah has been made aware of this problem on IRC and will hopefully be
 able to at least free some disk space (maybe 18th or 19th of May).

 But 2 questions remains:
 - could the root cause be identified to increase the availability and
 reduce the risk of corruption (if any)?
 - is there a backup to restore the data in case those would end being
 corrupted?

--

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4176#comment:1>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage