On Sunday 24 July 2005 03:44, Edward Shishkin wrote:
Edward Shishkin wrote:
David Masover wrote:
Ok, please explain what this actually means for users.
How will an FS made by the current reiser4progs be different than
that made by the new (patched) ones that will be coming out?
Edward Shishkin wrote:
David Masover wrote:
Ok, please explain what this actually means for users.
How will an FS made by the current reiser4progs be different than
that made by the new (patched) ones that will be coming out? Is the
new way better? If so, how can one take an existing
David Masover wrote:
Edward Shishkin wrote:
Hans Reiser wrote:
Edward Shishkin wrote:
David Masover wrote:
E.Gryaznova wrote:
Notification:
The reiser4 format was changed in reiser4-for-2.6.11-5.patch and new
reiser4 kernel code is able to handle the old format.
Edward Shishkin wrote:
David Masover wrote:
E.Gryaznova wrote:
Notification:
The reiser4 format was changed in reiser4-for-2.6.11-5.patch and new
reiser4 kernel code is able to handle the old format.
Good, so I don't have to reformat _immediately_...
But, why isn't it for 2.6.12
On 7/20/05, Edward Shishkin [EMAIL PROTECTED] wrote:
like other existing
ones. This will be a way to create cryptcompress files per superblock.
There is another
more flexible way (which is compatible with the previous one) to create
it per file/directory,
but it uses deprecated metas
Gregory Maxwell wrote:
Nonselective use of this feature will be nearly useless.
No, that is not true. Most users are not interested in specifying per
file whether we can compress it. So our plugin tries to compress the
first 64k, and if it fails to it assumes the file is not compressable.
Hans Reiser wrote:
Edward Shishkin wrote:
David Masover wrote:
E.Gryaznova wrote:
Notification:
The reiser4 format was changed in reiser4-for-2.6.11-5.patch and new
reiser4 kernel code is able to handle the old format.
Good, so I don't have to reformat
Edward Shishkin wrote:
Hans Reiser wrote:
Edward Shishkin wrote:
David Masover wrote:
E.Gryaznova wrote:
Notification:
The reiser4 format was changed in reiser4-for-2.6.11-5.patch and new
reiser4 kernel code is able to handle the old format.
Good, so I don't have
E.Gryaznova wrote:
Notification:
The reiser4 format was changed in reiser4-for-2.6.11-5.patch and new
reiser4 kernel code is able to handle the old format.
Good, so I don't have to reformat _immediately_...
But, why isn't it for 2.6.12 yet? We're already on at least 2.6.12.2,
last I
David Masover wrote:
E.Gryaznova wrote:
Notification:
The reiser4 format was changed in reiser4-for-2.6.11-5.patch and new
reiser4 kernel code is able to handle the old format.
Good, so I don't have to reformat _immediately_...
But, why isn't it for 2.6.12 yet? We're already on at
E.Gryaznova wrote:
Notification:
The reiser4 format was changed in reiser4-for-2.6.11-5.patch and new
reiser4 kernel code is able to handle the old format.
The reiser4progs-1.0.4 are not able to handle the format changes. The
fix for reiser4progs will be ready next week.
Thanks,
Lena
11 matches
Mail list logo
