--- The message cannot be delivered to the following address. ---
[EMAIL PROTECTED]Mailbox unknown or not accepting mail.
553 [EMAIL PROTECTED]... No such user [EMAIL PROTECTED]
Reporting-MTA: Symantec_AntiVirus_for_SMTP_Gateways_mailhost@nfic.com
Final-Recipient: rfc822;jtobey@banta-im.com
Alexander G. M. Smith writes:
Nikita Danilov wrote on Mon, 30 May 2005 15:00:52 +0400:
Nothing in VFS prevents files from supporting both read(2) and
readdir(3). The problem is with link(2): VFS assumes that directories
form _tree_, that is, every directory has well-defined parent.
Matthias Barremaecker wrote:
Hi,
Thanx for your reply.
The data is not THAT importend, all our importend data is backuped 4
times, inc. original (well, 3 times now, since the 1300gig machine is
broke).
I did a bit furtur reasearch and maybe this is something to think about
if you use
Hi Dan,
My recovery goes rather well...
Does the badblocks count or anything ? With me it counted.
You have to write the bad block no's to a file and feed that to the
reiserfschk.
I didn't completed a full badblock check coz I knew the badblocks could
only be at the beginning of the lvm
Nikita Danilov wrote:
Alexander G. M. Smith writes:
Nikita Danilov wrote on Mon, 30 May 2005 15:00:52 +0400:
Nothing in VFS prevents files from supporting both read(2) and
readdir(3). The problem is with link(2): VFS assumes that directories
form _tree_, that is, every directory has
Matthias Barremaecker wrote:
Hi Dan,
My recovery goes rather well...
Does the badblocks count or anything ? With me it counted.
So far, I haven't seen any bad blocks written to my output file. I'm
not in front of the machine (remote location), so I can't see what's on
the console, where
Hello Hans,
Hans Reiser writes:
Nikita Danilov wrote:
Alexander G. M. Smith writes:
Nikita Danilov wrote on Mon, 30 May 2005 15:00:52 +0400:
Nothing in VFS prevents files from supporting both read(2) and
readdir(3). The problem is with link(2): VFS assumes that directories
On Tue, 31 May 2005 08:04:42 PDT, Hans Reiser said:
Cycle may consists of more graph nodes than fits into memory.
There are pathname length restrictions already in the kernel that should
prevent that, yes?
The problem is that although a *single* pathname can't be longer than some
length,
unsubscribe
On Mon, 2005-05-30 at 01:19 -0700, Hans Reiser wrote:
[EMAIL PROTECTED] wrote:
On Fri, 27 May 2005 23:56:35 CDT, David Masover said:
Hans, comment please? Is this approaching v5 / v6 / Future Vision? It
does seem more than a little clunky when applied to v4...
Well, if you
On Tue, 2005-05-31 at 12:30 -0400, [EMAIL PROTECTED] wrote:
On Tue, 31 May 2005 08:04:42 PDT, Hans Reiser said:
Cycle may consists of more graph nodes than fits into memory.
There are pathname length restrictions already in the kernel that should
prevent that, yes?
The problem is
What happens when you unlink the True Name?
Hans
Jonathan Briggs wrote:
You can avoid cycles by redefining the problem.
Every file or data object has one single True Name which is their
inode or OID. Each data object then has one or more names as
properties. Names are either single strings
Jonathan Briggs wrote:
Why innovate in the filesystem though, when it would work just as well
or better in the VFS layer?
Why don't we just have one filesystem, think of the advantages.
;-)
I don't try to get other people to follow my lead anymore, I just ship
code that works. Putting it
Either that isn't allowed, or it immediately vanishes from all
directories.
If deleting by OID isn't allowed, then every name property must be
removed in order to delete the file.
Personally, I would allow deleting the OID. It would be a convenient
way to be sure every instance of a file was
On Tue, May 31, 2005 17:09, Dan Oglesby said:
So far, I haven't seen any bad blocks written to my output file. I'm
not in front of the machine (remote location), so I can't see what's on
the console, where I'm actually running the command.
use screendump(1) to see what's on the console. it
Hi everyone,
I'm looking into using reiser4 and it's encryption plugin on a number
of new CentOS4 servers I will be building. I've been doing various
searches via google and the list archives, and I've seen a few emails
from last year which indicated that the encryption plugin wasn't yet
ready
Jonathan Briggs writes:
On Tue, 2005-05-31 at 12:30 -0400, [EMAIL PROTECTED] wrote:
On Tue, 31 May 2005 08:04:42 PDT, Hans Reiser said:
Cycle may consists of more graph nodes than fits into memory.
There are pathname length restrictions already in the kernel that should
Well,. if you allow multiple true names, then you start to resemble
something I suggested a few years ago, in which I outlined a taxonomy of
links, and suggested that some links would count towards the reference
count and some would not.
Of course, that does nothing for the cycle problem..
ADT wrote:
Hi everyone,
I'm looking into using reiser4 and it's encryption plugin on a number
of new CentOS4 servers I will be building. I've been doing various
searches via google and the list archives, and I've seen a few emails
from last year which indicated that the encryption plugin
What about if we have it that only the first name a directory is created
with counts towards its reference count, and that if the directory is
moved if it is moved from its first name, the new name becomes the one
that counts towards the reference count? A bit of a hack, but would work.
Hans
I'm trying to create a reiser4 filesystem on a ~4tb block device,
but I'm getting the error Fatal: The partition size is too big. The FAQ
seems to list a max filesystem size of 16tb. Am I missing something?
diablo:~# mkreiser4 /dev/sda3
mkreiser4 1.0.4
Copyright (C) 2001, 2002, 2003,
Wish you could be better?
http://www.jnaz.net/ss/
Power is the ability not to have to please.
The man who has confidence in himself gains the confidence of others.
Everybody should be able to make some music...That's the cosmic dance!
Nothing is at last sacred but the integrity of
On Tue, 2005-05-31 at 15:01 -0600, Jonathan Briggs wrote:
I should create an example.
Wherever I used True Name previously, use OID instead. True Name was
simply another term for a unique object identifier.
Three files with OIDs of 1001, 1002, and 1003.
Object 1001:
name: /tmp/A/file1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Edward Shishkin wrote:
ADT wrote:
Hi everyone,
I'm looking into using reiser4 and it's encryption plugin on a number
of new CentOS4 servers I will be building. I've been doing various
searches via google and the list archives, and I've seen a
Jonathan Briggs writes:
On Tue, 2005-05-31 at 15:01 -0600, Jonathan Briggs wrote:
I should create an example.
Wherever I used True Name previously, use OID instead. True Name was
simply another term for a unique object identifier.
Three files with OIDs of 1001, 1002, and
On Wed, 2005-06-01 at 02:36 +0400, Nikita Danilov wrote:
Jonathan Briggs writes:
On Tue, 2005-05-31 at 15:01 -0600, Jonathan Briggs wrote:
I should create an example.
Wherever I used True Name previously, use OID instead. True Name was
simply another term for a unique object
Nikita Danilov wrote on Tue, 31 May 2005 13:34:55 +0400:
Cycle may consists of more graph nodes than fits into memory. Cycle
detection is crucial for rename semantics, and if
cycle-just-about-to-be-formed doesn't fit into memory it's not clear how
to detect it, because tree has to be locked
27 matches
Mail list logo
