Re: For review: NAND out of space patch.

2008-07-22 Thread Martin Langhoff
On Wed, Jul 23, 2008 at 11:04 AM, Michael Stone <[EMAIL PROTECTED]> wrote: > On Tue, Jul 22, 2008 at 06:54:24PM -0400, Eben Eliason wrote: >>> >>> If you mean "user files" then the problem is that there is never a >>> correct heuristic. > > Please remember that the only goal that this work MUST ach

Re: For review: NAND out of space patch.

2008-07-22 Thread Michael Stone
On Tue, Jul 22, 2008 at 06:54:24PM -0400, Eben Eliason wrote: >> If you mean "user files" then the problem is that there is never a >> correct heuristic. Please remember that the only goal that this work MUST achieve is to be less costly to our deployments and less painful to kids than a FULL REF

Re: For review: NAND out of space patch.

2008-07-22 Thread Eben Eliason
On Tue, Jul 22, 2008 at 6:45 PM, Martin Langhoff <[EMAIL PROTECTED]> wrote: > On Wed, Jul 23, 2008 at 10:38 AM, Eben Eliason <[EMAIL PROTECTED]> > wrote: > > But, assuming we can actually boot into usable Sugar, we've solved almost > > half the battle, since the non-modal alert can then strongly e

Re: For review: NAND out of space patch.

2008-07-22 Thread Carol Lerche
Perhaps the browser should police transfer size on download and check for sufficient space before proceeding? I'm guessing this would eliminate most of the out-of-space conditions prospectively, though it doesn't remove the need to provide the "get out of jail" solution that has been the topic of

Re: For review: NAND out of space patch.

2008-07-22 Thread Martin Langhoff
On Wed, Jul 23, 2008 at 10:38 AM, Eben Eliason <[EMAIL PROTECTED]> wrote: > But, assuming we can actually boot into usable Sugar, we've solved almost > half the battle, since the non-modal alert can then strongly encourage the > user to deal with the issue. It's not the flat out guarantee we need

Re: For review: NAND out of space patch.

2008-07-22 Thread Eben Eliason
But, assuming we can actually boot into usable Sugar, we've solved almost half the battle, since the non-modal alert can then strongly encourage the user to deal with the issue. It's not the flat out guarantee we need to have, but it's a pretty darn good usable solution for many cases. Mostly, th

Re: For review: NAND out of space patch.

2008-07-22 Thread Chris Ball
Hi Martin, > how about removing obvious cache files instead - so we can combine > this with Erik's? /var/cache has several candidates we know are > safe (yum dirs) and > .sugar/default/org.laptop.WebActivity/data/gecko/Cache/ I'm happy to do this *as well*, and should probably also lo

Re: For review: NAND out of space patch.

2008-07-22 Thread Martin Langhoff
On Tue, Jul 22, 2008 at 2:21 PM, Chris Ball <[EMAIL PROTECTED]> wrote: > Here's a small Python script that acts as a final fail-safe in the event Chris, how about removing obvious cache files instead - so we can combine this with Erik's? /var/cache has several candidates we know are safe (yum dir

Re: For review: NAND out of space patch.

2008-07-22 Thread Gary C Martin
On 22 Jul 2008, at 17:03, John Watlington wrote: > > On Jul 22, 2008, at 12:59 PM, Tomeu Vizoso wrote: > >> On Tue, Jul 22, 2008 at 5:53 PM, John Watlington <[EMAIL PROTECTED]> >> wrote: >>> >>> I'm getting three images right now. >>> >>> One of the machines booted, but wouldn't allow any activiti

Re: For review: NAND out of space patch.

2008-07-22 Thread Martin Langhoff
On Wed, Jul 23, 2008 at 8:05 AM, C. Scott Ananian <[EMAIL PROTECTED]> wrote: > For the record, I oppose the unionfs solution for the "real fix", Erik's solution is not the real fix but it is better than cjb's - if he can get it going soon, even with a dialogue on start up saying "delete something!

Re: For review: NAND out of space patch.

2008-07-22 Thread Erik Garrison
On Tue, Jul 22, 2008 at 02:38:22PM +0200, Morgan Collett wrote: > On Tue, Jul 22, 2008 at 04:21, Chris Ball <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Here's a small Python script that acts as a final fail-safe in the event > > that the datastore is full and we can't boot because of it, by deleting

Re: For review: NAND out of space patch.

2008-07-22 Thread Erik Garrison
On Tue, Jul 22, 2008 at 04:05:33PM -0400, C. Scott Ananian wrote: > We should distinguish at least three solution spaces: > a) UY's solution, based on a small patch to 656 > b) A solution to include in 8.2 > c) The "real" solution, in case there are limits to what we can do for 8.2. > > cjb's p

Re: For review: NAND out of space patch.

2008-07-22 Thread Eben Eliason
On Tue, Jul 22, 2008 at 4:26 PM, Gary C Martin <[EMAIL PROTECTED]> wrote: > On 22 Jul 2008, at 13:38, Morgan Collett wrote: > > > Another approach of which I vaguely remember discussion, is be > > deleting activities instead of data. (Except for Browse, and > > Terminal... so you can possibly get

Re: For review: NAND out of space patch.

2008-07-22 Thread Gary C Martin
On 22 Jul 2008, at 13:38, Morgan Collett wrote: > Another approach of which I vaguely remember discussion, is be > deleting activities instead of data. (Except for Browse, and > Terminal... so you can possibly get them back again!) > > There would then be a symptom which they would hopefully notic

Re: For review: NAND out of space patch.

2008-07-22 Thread C. Scott Ananian
We should distinguish at least three solution spaces: a) UY's solution, based on a small patch to 656 b) A solution to include in 8.2 c) The "real" solution, in case there are limits to what we can do for 8.2. cjb's patch is primarily for (a), with applications to (b) and *perhaps* as a fail-sa

Re: For review: NAND out of space patch.

2008-07-22 Thread Tomeu Vizoso
On Tue, Jul 22, 2008 at 4:21 AM, Chris Ball <[EMAIL PROTECTED]> wrote: > * Deleting a file from the datastore doesn't delete its entry in the > index. Resuming a Journal entry with no corresponding file usually > produces a blank document in the activity being resumed. This may be easy

Re: For review: NAND out of space patch.

2008-07-22 Thread Tomeu Vizoso
On Tue, Jul 22, 2008 at 8:28 PM, Jim Gettys <[EMAIL PROTECTED]> wrote: > The simplest UI would be a size-sorted view of the journal. We could do something like this easily without accessing the DS, now that we have the metadata in json files. Eben, ideas? Thanks, Tomeu _

Re: For review: NAND out of space patch.

2008-07-22 Thread Tomeu Vizoso
On Tue, Jul 22, 2008 at 8:26 PM, Erik Garrison <[EMAIL PROTECTED]> wrote: > On Tue, Jul 22, 2008 at 01:58:29PM -0400, [EMAIL PROTECTED] wrote: >> jim wrote: >> > Ah, I like this idea better than the previous I've heard; if we can >> > uninstall software or cleanup the journal with human intervent

Re: For review: NAND out of space patch.

2008-07-22 Thread Jim Gettys
The simplest UI would be a size-sorted view of the journal. - Jim On Tue, 2008-07-22 at 14:26 -0400, Erik Garrison wrote: > On Tue, Jul 22, 2008 at 01:58:29PM -0400, [EMAIL PROTECTED] wrote: > > jim wrote: > > > Ah, I like this idea better than the previous I've heard; i

Re: For review: NAND out of space patch.

2008-07-22 Thread Erik Garrison
On Tue, Jul 22, 2008 at 01:58:29PM -0400, [EMAIL PROTECTED] wrote: > jim wrote: > > Ah, I like this idea better than the previous I've heard; if we can > > uninstall software or cleanup the journal with human intervention, that > > would be good I'm nervous about automatic cleanup schemes..

Re: For review: NAND out of space patch.

2008-07-22 Thread John Watlington
On Jul 22, 2008, at 2:23 PM, Jim Gettys wrote: > Ah, I like this idea better than the previous I've heard; if we can > uninstall software or cleanup the journal with human intervention, > that > would be good I'm nervous about automatic cleanup schemes >- Jim A

Re: For review: NAND out of space patch.

2008-07-22 Thread pgf
jim wrote: > Ah, I like this idea better than the previous I've heard; if we can > uninstall software or cleanup the journal with human intervention, that > would be good I'm nervous about automatic cleanup schemes i agree that erik's proposal sounds attractive, since we'd have most or

Re: For review: NAND out of space patch.

2008-07-22 Thread Deepak Saxena
On Jul 22 2008, at 11:36, Chris Ball was caught saying: > During this reboot is where we delete some files. I think the > deployments probably run pretty-boot and don't see text messages, > so these users won't see anything different at all. If they did > see text messages during boot, they would

Re: For review: NAND out of space patch.

2008-07-22 Thread Jim Gettys
Ah, I like this idea better than the previous I've heard; if we can uninstall software or cleanup the journal with human intervention, that would be good I'm nervous about automatic cleanup schemes - Jim On Tue, 2008-07-22 at 13:20 -0400, Erik Garrison wrote: > On

Re: For review: NAND out of space patch.

2008-07-22 Thread Erik Garrison
On Tue, Jul 22, 2008 at 12:53:37PM -0300, John Watlington wrote: > > On Jul 22, 2008, at 12:06 PM, Chris Ball wrote: > > > Hi, > > > >> Can you walk me through the exact steps that the user would > >> experience if this script was installed? > > > > They wouldn't see anything different, but Journ

Re: For review: NAND out of space patch.

2008-07-22 Thread John Watlington
On Jul 22, 2008, at 12:59 PM, Tomeu Vizoso wrote: > On Tue, Jul 22, 2008 at 5:53 PM, John Watlington <[EMAIL PROTECTED]> > wrote: >> >> I'm getting three images right now. >> >> One of the machines booted, but wouldn't allow any activities to >> launch >> (which since you can't log in on vtty

Re: For review: NAND out of space patch.

2008-07-22 Thread Tomeu Vizoso
On Tue, Jul 22, 2008 at 5:53 PM, John Watlington <[EMAIL PROTECTED]> wrote: > > I'm getting three images right now. > > One of the machines booted, but wouldn't allow any activities to launch > (which since you can't log in on vttys kinda locks down the machine). > But I did notice a large number o

Re: For review: NAND out of space patch.

2008-07-22 Thread John Watlington
On Jul 22, 2008, at 12:06 PM, Chris Ball wrote: > Hi, > >> Can you walk me through the exact steps that the user would >> experience if this script was installed? > > They wouldn't see anything different, but Journal entries > corresponding > to files we chose to delete wouldn't resume properly

Re: For review: NAND out of space patch.

2008-07-22 Thread Chris Ball
Hi, It's run at boot, so: > - I sit down in the morning, start my XO (anything happen here?) Only if you're already below the disk space threshold. > - I download some stuff off the internet. I fill my NAND (anything > happen here?) No. > - My XO slows to a crawl so I reboot (anyt

Re: For review: NAND out of space patch.

2008-07-22 Thread Greg Smith
Hi Chris et al, OK, we're checking how. Hopefully Wad will have some data and I'm trying to get two 656 XOs in the office filled up so I can see the failure case. I still don't understand when and how the script is used. Please give me a little more detail. e.g. - I sit down in the morning, st

Re: For review: NAND out of space patch.

2008-07-22 Thread Tomeu Vizoso
On Tue, Jul 22, 2008 at 5:06 PM, Chris Ball <[EMAIL PROTECTED]> wrote: > > Since we disagree, maybe best to wait until we have some disk-full > images back from the field so that we can see what used up all the > space, before deciding the algorithm. Yeah, I'm still a bit lost regarding this. Let'

Re: For review: NAND out of space patch.

2008-07-22 Thread Chris Ball
Hi, > Can you walk me through the exact steps that the user would > experience if this script was installed? They wouldn't see anything different, but Journal entries corresponding to files we chose to delete wouldn't resume properly. > In terms of which files, I think the oldest (or

Re: For review: NAND out of space patch.

2008-07-22 Thread Morgan Collett
On Tue, Jul 22, 2008 at 04:21, Chris Ball <[EMAIL PROTECTED]> wrote: > Hi, > > Here's a small Python script that acts as a final fail-safe in the event > that the datastore is full and we can't boot because of it, by deleting > datastore files largest-first until we cross a threshold of how much >

Re: For review: NAND out of space patch.

2008-07-22 Thread Greg Smith
33 -0400 > From: Chris Ball <[EMAIL PROTECTED]> > Subject: For review: NAND out of space patch. > To: devel@lists.laptop.org > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=us-ascii > > Hi, > > Here's a small Python script th

Re: For review: NAND out of space patch.

2008-07-21 Thread pgf
chris wrote: > Hi, > >> I'll go on record repeating the comments made earlier. deleting the >> students largest file is probably deleting their most important >> work. > > Of course, it should be only a last resort; I tried to make that clear. > I hope that in 8.2 we'll fix th

Re: For review: NAND out of space patch.

2008-07-21 Thread Benjamin M. Schwartz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: | I'll go on record repeating the comments made earlier. deleting the | students largest file is probably deleting their most important work. | deleting anything the student made should be a last resort (and should | probably g

Re: For review: NAND out of space patch.

2008-07-21 Thread Chris Ball
Hi, > I'll go on record repeating the comments made earlier. deleting the > students largest file is probably deleting their most important > work. Of course, it should be only a last resort; I tried to make that clear. I hope that in 8.2 we'll fix the problem in general, in a way that p

Re: For review: NAND out of space patch.

2008-07-21 Thread david
On Mon, 21 Jul 2008, Chris Ball wrote: > Hi, > > Here's a small Python script that acts as a final fail-safe in the event > that the datastore is full and we can't boot because of it, by deleting > datastore files largest-first until we cross a threshold of how much > free space is "enough". It c

For review: NAND out of space patch.

2008-07-21 Thread Chris Ball
Hi, Here's a small Python script that acts as a final fail-safe in the event that the datastore is full and we can't boot because of it, by deleting datastore files largest-first until we cross a threshold of how much free space is "enough". It could be incorporated into the Python init process.