Re: write support without inodes

2000-05-13 Thread Thomas Bushnell, BSG
Marcus Brinkmann <[EMAIL PROTECTED]> writes: > Do you have any other tips for this situation, things to watch out for, or > strategies how to get the location of the directory entry (seems I need a > lookup at update time, because the address is not robust under rename > operations (moving the fi

Re: write support without inodes

2000-05-13 Thread Thomas Bushnell, BSG
Marcus Brinkmann <[EMAIL PROTECTED]> writes: > Do I need some lock on the directory node when updating the node > information? Yes, I think that would be necessary. But only when you actually write it out to disk, in the diskfs_write_disknode routine. Just acquire the regular directory lock.

Re: write support without inodes

2000-05-08 Thread Marcus Brinkmann
(ugh, following up to my own mail a second time ;) On Mon, 08 May 2000 00:53:46 Marcus Brinkmann wrote: > The other direction seems to work, though. Currently, in the node cache, I > hold the dirent (directory entry) address in disk_image. I think I can move the struct dirrect * to the disknode

Re: write support without inodes

2000-05-07 Thread Marcus Brinkmann
Hi, the linux code didn't reveal much to me, they seem to store the address of the directory entry as the inode. This has the problem that renaming the file (possibly moving the dirent address) invalidates the inode number. Not good for us (we use the inode number for caching, for example). The

Re: write support without inodes

2000-05-07 Thread Jeff Bailey
On Sun, May 07, 2000 at 10:27:17PM +0200, Marcus Brinkmann wrote: > Do you have any other tips for this situation, things to watch out for, or > strategies how to get the location of the directory entry (seems I need a > lookup at update time, because the address is not robust under rename > oper

Re: write support without inodes

2000-05-07 Thread Mark Kettenis
Date: Sun, 7 May 2000 22:27:17 +0200 From: Marcus Brinkmann <[EMAIL PROTECTED]> Hi, as you may know, there are no inodes in the FATFS, all information being stored directly in the directory entry. Do I need some lock on the directory node when updating the node information?

write support without inodes

2000-05-07 Thread Marcus Brinkmann
Hi, as you may know, there are no inodes in the FATFS, all information being stored directly in the directory entry. Do I need some lock on the directory node when updating the node information? Do you have any other tips for this situation, things to watch out for, or strategies how to get the