9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Iruatã Souza" <iru.muzgo@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] full fossil follies
Date: Fri, 25 Jun 2021 19:23:07 +0200	[thread overview]
Message-ID: <CABJnqBQCzV3Zjo1NftytqjAbnKZp9GwjODUDjJ-3hqVqU6Sc1A@mail.gmail.com> (raw)
In-Reply-To: <20210625151739.GA11215@polynum.com>

[-- Attachment #1: Type: text/plain, Size: 2477 bytes --]

Le ven. 25 juin 2021 à 17:19, <tlaronde@polynum.com> a écrit :

> On Fri, Jun 25, 2021 at 02:12:07PM +0000, adr via 9fans wrote:
> > On Fri, Jun 25, 2021 at 01:41:30PM +0100, Richard Miller wrote:
> > > > it just becomes difficult
> > > > to do anything when no fossil blocks can be allocated
> > >
> > > Thinking a bit further about this: intuitively one might expect to be
> > > able to reboot using a local file system which is completely full, and
> > > use du and ls to find big files and rm to delete them, without the need
> > > to allocate new blocks. Something in the way fossil works, makes this
> > > impossible at present. I wonder how much work it would be to
> investigate
> > > and fix?
> >
> > I haven't studied how fossil works, so excuse this light chat.
> > Couldn't fossil have reserved blocks so when it starts and it's
> > full it can add those block and present the user to a recovery
> > session? Just a console session printing the last file modified?
>
> I don't think I will tell anybody a scoop, but it is what is present in
> traditional Unix filesystems where there is a percent of the storage
> preserved... but for root, user under which you are not supposed to
> log to the system in normal operation. This is probably the problem:
> since there is no privileged user, for "whom" to preserve/reserve these
> blocks?
>
> I imagine the alternative would be, if fossil reports full, that memory
> filesystems should be mounted on top of the system mandatory writable
> dirs so that the system will not block but normal booting will not
> be done but the program launched will be one requiring user to make
> room, crucial infos written in memory filesystems being copied back
> to fossil when done. But it is easier to implement when booting/rebooting,
> but more problematic if the system is running. Except perhaps that
> there will always be a memory filesystem mounted with rescue
> programs/scripts that the user can precisely use when the system
> is out of disk space, utilities that write nothing to disk (but just in
> their memory realm), in order to not paint oneself in a corner.
>

FWIW in 9front you can jump into rc while booting and fix this sort of
issue.


------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T4ec62ed03a91d7a4-Mec344f9c69bd216b67f824c4
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 3645 bytes --]

  parent reply	other threads:[~2021-06-25 17:23 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23 19:11 [9fans] p9f mention of 9front hiro
2021-06-23 23:05 ` unobe
2021-06-23 23:35   ` Sigrid Solveig Haflínudóttir
2021-06-23 23:58     ` Romano
2021-06-24  4:06       ` Lucio De Re
2021-06-24  4:56         ` unobe
2021-06-24  5:52           ` Lucio De Re
2021-06-24 21:25             ` Wes Kussmaul
2021-06-24 23:29               ` silas poulson
2021-06-25 13:06                 ` Wes Kussmaul
2021-06-24  8:24         ` Frank D. Engel, Jr.
2021-06-24  9:25           ` [9fans] plan9 and touch screens Richard Miller
2021-06-24  9:59             ` Lucio De Re
2021-06-24 10:12           ` [9fans] p9f mention of 9front Philip Silva via 9fans
2021-06-24 16:05             ` unobe
2021-06-24 16:16             ` Ethan Gardener
2021-06-24 11:19   ` hiro
2021-06-24 15:01     ` AW: " sirjofri
2021-06-24 20:51     ` unobe
2021-06-25  8:28       ` Steve Simon
2021-06-25  9:31         ` Richard Miller
2021-06-25 12:41           ` [9fans] full fossil follies Richard Miller
2021-06-25 14:12             ` adr via 9fans
2021-06-25 15:17               ` tlaronde
2021-06-25 16:06                 ` adr via 9fans
2021-06-25 16:45                   ` adr via 9fans
2021-06-26  9:01                     ` Ethan Gardener
2021-06-25 17:23                 ` Iruatã Souza [this message]
2021-06-26  8:56                   ` Richard Miller
2021-06-26  8:34       ` [9fans] p9f mention of 9front Ethan Gardener
2021-06-26 12:55         ` noam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABJnqBQCzV3Zjo1NftytqjAbnKZp9GwjODUDjJ-3hqVqU6Sc1A@mail.gmail.com \
    --to=iru.muzgo@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).