Re: ReiserFS v3 choking when free space falls below 10%?

2006-07-07 Thread Hans Reiser
Guys, if you run the kernel under a debugger, and get it to where you see the excessive CPU usage, and then start stepping through the bitmap code, I am sure it will be very obvious what the error is. Can anyone do that for us? Jeff?

Re: ReiserFS v3 choking when free space falls below 10%?

2006-07-07 Thread Mike Benoit
On Fri, 2006-07-07 at 19:49 +0200, Jan Kara wrote: > Hi, > > just one note: I've looked to the in scan_bitmap() in bitmap.c. There is: > /* When the bitmap is more than 10% free, anyone can allocate. > * When it's less than 10% free, only files that already use the >

Re: ReiserFS v3 choking when free space falls below 10%?

2006-07-07 Thread Mike Benoit
On Fri, 2006-07-07 at 19:49 +0200, Jan Kara wrote: > Hi, > > just one note: I've looked to the in scan_bitmap() in bitmap.c. There is: > /* When the bitmap is more than 10% free, anyone can allocate. > * When it's less than 10% free, only files that already use the >

Re: ReiserFS v3 choking when free space falls below 10%?

2006-07-07 Thread Hans Reiser
Jan Kara wrote: >>Jan Kara wrote: >> >> >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jan Kara wrote: > Hi, > > just one note: I've looked to the in scan_bitmap() in bitmap.c. There is: > /* When the bitmap is more than 1

Re: ReiserFS v3 choking when free space falls below 10%?

2006-07-07 Thread Jan Kara
> Jan Kara wrote: > > >>-BEGIN PGP SIGNED MESSAGE- > >>Hash: SHA1 > >> > >>Jan Kara wrote: > >> > >> > >>> Hi, > >>> > >>> just one note: I've looked to the in scan_bitmap() in bitmap.c. There is: > >>>/* When the bitmap is more than 10% free, anyone can allocate. > >>>

Re: ReiserFS v3 choking when free space falls below 10%?

2006-07-07 Thread Hans Reiser
Jan Kara wrote: >>-BEGIN PGP SIGNED MESSAGE- >>Hash: SHA1 >> >>Jan Kara wrote: >> >> >>> Hi, >>> >>> just one note: I've looked to the in scan_bitmap() in bitmap.c. There is: >>>/* When the bitmap is more than 10% free, anyone can allocate. >>> * When it's less than 1

Re: ReiserFS v3 choking when free space falls below 10%?

2006-07-07 Thread Jeff Mahoney
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jan Kara wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Jan Kara wrote: >>> Hi, >>> >>> just one note: I've looked to the in scan_bitmap() in bitmap.c. There is: >>> /* When the bitmap is more than 10% free, anyone can all

Re: ReiserFS v3 choking when free space falls below 10%?

2006-07-07 Thread Jan Kara
> -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Jan Kara wrote: > > Hi, > > > > just one note: I've looked to the in scan_bitmap() in bitmap.c. There is: > > /* When the bitmap is more than 10% free, anyone can allocate. > > * When it's less than 10% free, only files th

Re: ReiserFS v3 choking when free space falls below 10%?

2006-07-07 Thread Jeff Mahoney
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jan Kara wrote: > Hi, > > just one note: I've looked to the in scan_bitmap() in bitmap.c. There is: > /* When the bitmap is more than 10% free, anyone can allocate. > * When it's less than 10% free, only files that already use the

Re: ReiserFS v3 choking when free space falls below 10%?

2006-07-07 Thread Jan Kara
Hi, just one note: I've looked to the in scan_bitmap() in bitmap.c. There is: /* When the bitmap is more than 10% free, anyone can allocate. * When it's less than 10% free, only files that already use the * bitmap are allowed. Once we pass 80% full, this restriction

Re: reiser4 oops

2006-07-07 Thread Vladimir V. Saveliev
Hello On Fri, 2006-07-07 at 01:18 -0600, Jake Maciejewski wrote: > It doesn't look like this issue has been fixed: > > http://people.msoe.edu/~maciejej/patches/AMD64_reiser4_debug/20060702/reiser4_kio_http.txt.gz > > Again fsck showed a clean filesystem. Should I try -mm? > Yes, please try to

Re: ReiserFS v3 choking when free space falls below 10%?

2006-07-07 Thread Mike Benoit
Hi Jeff, Like clock work the problem showed up pretty much exactly when I expected. This time however I discovered a few other interesting tidbits along the way. I tried to re-create the problem much faster by writing a little script that would append data to a file at about 5mb/s, I ran