NANDFS eats itself up

Ronald Klop ronald-freebsd8 at klop.yi.org
Fri May 17 11:49:03 UTC 2013


On Thu, 07 Feb 2013 10:41:11 +0100, Ronald Klop  
<ronald-freebsd8 at klop.yi.org> wrote:

> On Fri, 04 Jan 2013 00:54:51 +0100, Mateusz Guzik <mjguzik at gmail.com>  
> wrote:
>
>> On Thu, Nov 29, 2012 at 01:13:55PM +0200, Boris Astardzhiev wrote:
>>> > On Wed, Nov 28, 2012 at 05:36:11PM +0200, Boris Astardzhiev wrote:
>>> > > If I do that I might be unable to set back the verbose level to 0  
>>> since
>>> > the
>>> > > output is very very NOISY. This means that I will have to start  
>>> again
>>> > from
>>> > > the beginning if I need to reproduce it. Nevertheless here you go.  
>>> Check
>>> > > the attachment (OUTPUTNAND.txt.bz2).
>>> > >
>>> >
>>> > I think I reproduced your problem. Possibly I'll have time to work on
>>> > this next week, but no promises.
>>> >
>>
>> So, I think I understand what is causing the problem here and will most
>> likely have time to work on it this month.
>>
>
> Hi,
>
> Not to push you or something like that, but did you find the time?
> I'm curious to running my SHEEVAPLUG using the NAND memory.
> If there is something to test or help in another way, I'm willing to do  
> that.
>
> Ronald.
> _______________________________________________
> freebsd-fs at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail to "freebsd-fs-unsubscribe at freebsd.org"
>

Hi,

This full thread is available here.
http://freebsd.1045724.n5.nabble.com/NANDFS-eats-itself-up-td5764878.html

I follow the commits on FreeBSD, but did not see a fix for this. Maybe I  
missed it. I'm wondering if there is something news about this issue.
I understand everybody is very busy, but am curious about it.

Regards,
Ronald.


More information about the freebsd-fs mailing list