Re: reiser4: reserved disk space

[Ignatich]

Hello Edward,

Thank you for explanation. I'm still not convinced though. Cryptcompress 
is indeed awesome, but that doesn't change the fact that reserved block 
calculation can be improved. 5% of modern 500GB drive is 25GB and I 
can't see how that space will ever be used even if I will delete 
thousands of files. There is no point in reserving disk space if it will 
never be used. There are many ways to improve this situation: a upper 
and lower limit for reserved block count can be used, ability to 
manually set reserve can be added to mkfs or perhaps reserve usage 
patterns for various workloads can be analyzed and smarter algorithm can 
be developed.


Can you suggest how to simulate workload that will expose reserve block 
starvation?


Looking forward to your reply,
   Max Yudin

[Fwd: reiser4 bugs in 2.6.21-rc4]

[Ignatich]

---BeginMessage---

There are two bugs I found in current -mm reiser4 code.

1. Some files seem to be zeroed out randomly. Usually it's 
/lib/security/pam_limits.so and /lib/security/pam_deny.so. As 
fsck.reiser4 didn't find anything wrong I decided to create clean 
installation in vmware and see if this bug appears on newly formatted 
partition. It did.


2. Sometimes I get oppses in reiser4_do_readpage_extent. Assert codes 
are vs-1426 and nikita-2688. A patch was posted on namesys list to 
address this problem, but it didn't help.


Kernel: 2.6.21-rc4 with manually applied reiser4 patches from -mm. Arch: 
x86-64


---End Message---