Re: compression/reiser4.1

2005-03-14 Thread Clemens Eisserer
Hi there! I just read the discussion about the compression-plugin and I just wanted to say that this feature is something I really always missed under Linux when looking to NTFS. Its really great to see progress in this area! When do you think reiser4.1 will be ready? Thanks a lot, Clemens Ei

Our Company decide to bid you absolutely unexampled model of Blancpain watches. Prime offer for you.

2005-03-14 Thread Archibald Ualgctrp
Travel our company website, we offer prime discounts and great number of marques available, for instance Eberhard, Chopard or Vacheron Constantin. http://ommdnientve.aaiy.com/r/vron/beggshwigglop.pl

Re: umount and sync delays

2005-03-14 Thread Gorazd Golob
I have no idea, and so I must guess. I guess that if you try the same application on a different computer it will work reasonably fast and that the problem is hardware doing extensive retries. We have tests on ext3 and it wasn't like fast, but few minutes, not 30 minutes.. Or, you are doing comp

Re: BUG in submit_ordered_buffer at fs/reiserfs/journal.c:616!

2005-03-14 Thread Chris Mason
On Friday 11 March 2005 18:39, Hans Reiser wrote: > "I/O errors usually indicate bad hardware not bad software, > probably you need to get a new disk and use dd_rescue to copy everything This is your user friendly error message targeted at users that don't know what an I/O error is? What's an

Re: What is the official Reiser 4 ...

2005-03-14 Thread Hans Reiser
Dr. Giovanni A. Orlando wrote: > Hi, > >Some days ago I hear aboout the Reser 4.1. > >Is this true? > >Have Reiser4 moved to a new release? Not yet. 4.1 is entering alpha test. Some details are at www.namesys.com/blackbox_security.html > > Thanks, > Giovanni. >

Re: umount and sync delays

2005-03-14 Thread Hans Reiser
Gorazd Golob wrote: > Hi! > >>> >> Probably you just have a lot of dirty buffers in RAM and they need to >> flush to disk? >> > Hmm.. I'll try explain .. Before I did sync or unmount, application, > that previosly wrote to reiser4 partition was closed. In moment of > running sync or umount OS had

What is the official Reiser 4 ...

2005-03-14 Thread Dr. Giovanni A. Orlando
Hi, Some days ago I hear aboout the Reser 4.1. Is this true? Have Reiser4 moved to a new release? Thanks, Giovanni. -- -- -- Check FT Websites ... http://www.futuretg.com - ftp://ftp.futuretg.com http://www.FTLinuxCourse.com http://www.FTLinuxCourse.com/Certification http://www.rpmpara

Re: umount and sync delays

2005-03-14 Thread Gorazd Golob
Hi! Probably you just have a lot of dirty buffers in RAM and they need to flush to disk? Hmm.. I'll try explain .. Before I did sync or unmount, application, that previosly wrote to reiser4 partition was closed. In moment of running sync or umount OS had about 1.7gb of data in cache memory. Sync

Re: umount and sync delays

2005-03-14 Thread Hans Reiser
Gorazd Golob wrote: > hi! > > I have strangely long delay (still waiting at the time) when > unmounting or syncing partition with reiser4. At the same time writes > are occuring to disk subsystem - when checking vmstat and of course > checking disk activity light ;). > > Why does it take so long a

Re: Large Filesystem Support?

2005-03-14 Thread Vitaly Fertman
Hello, what your configure tells about _FILE_OFFSET_BITS & _LARGE_FILES? if it cannot detect the right value, probably the attached patches for configure.in would help. -- Thanks, Vitaly Fertman On Sunday 13 March 2005 12:13, Naveen Nathan wrote: > Hey Reiser team & fellow Reiser users. > >

umount and sync delays

2005-03-14 Thread Gorazd Golob
hi! I have strangely long delay (still waiting at the time) when unmounting or syncing partition with reiser4. At the same time writes are occuring to disk subsystem - when checking vmstat and of course checking disk activity light ;). Why does it take so long and it will ever finish ?:) I don'

Re: how to linking and traversing the inmemory tree

2005-03-14 Thread Edward Shishkin
siddharth kothari wrote: Hello hi. i am trying to create an in-memory for Reiser4. from the code i understand the following: 1) Znode is the inmemory representation of the actual node. 2) children have pointers to thier parents and alsso maintain their position in parents. 3) Znodes also have the