On Sat, 4 Sep 2004, Ara.T.Howard wrote:

On Fri, 3 Sep 2004, John LeSueur wrote:

I think this file is created everytime you start a transaction. Maybe even
if you only perform read only commands. The journal is what is used to keep
track of the changes to the database. Anyone else have any thoughts?

yes - it is. the thing is, unless a remote client unlinks it while another client has it open the sillynames would not appear. i can post a copy of one of the sillynamed files - but they are definitely the contents of db-journal. the question is why this is happening. running strace and looking at the fcntl lock calls lead me to think it __should__ be impossible for any client to unlink this file before someone else closed it - but that IS what i'm seeing happen...

here's a snaphshot of my system in action:


yacht:~/shared > new q total 4432 -rw-rw-rw- 1 cfadmin cfadmin 1023 Aug 29 08:55 db.schema drwxrwxrwx 11 cfadmin 11113 4096 Sep 4 15:43 .. -rw-rw-rw- 1 cfadmin cfadmin 4441088 Sep 4 15:44 db -rw------- 1 cfadmin cfadmin 21692 Sep 4 15:44 .nfs0091c0d400001089 -rw-rw-rw- 1 cfadmin cfadmin 0 Sep 4 15:44 lock -rw------- 1 cfadmin cfadmin 15500 Sep 4 15:44 .nfs0091c0d7000011c2 -rw-r--r-- 1 cfadmin cfadmin 0 Sep 4 15:44 trout.ngdc.noaa.gov.22069.lock.w -rw-r--r-- 1 cfadmin cfadmin 0 Sep 4 15:44 mahi.ngdc.noaa.gov.31335.waiting.w -rw------- 1 cfadmin cfadmin 15500 Sep 4 15:44 db-journal -rw------- 1 cfadmin cfadmin 8276 Sep 4 15:44 .nfs0091c0d500001270 drwxrwxrwx 2 cfadmin cfadmin 4096 Sep 4 15:44 .


you can see that the files

  .nfs0091c0d7000011c2

and

  db-journal

are (amost positively) the same.


so, somehow, the unlinking of the db-journal causes this behaviour.

-a
--
===============================================================================
| EMAIL :: Ara [dot] T [dot] Howard [at] noaa [dot] gov
| PHONE :: 303.497.6469
| A flower falls, even though we love it;
| and a weed grows, even though we do not love it. | --Dogen
===============================================================================

Reply via email to