Er whatever other issues may or may not be associated with ReiserFS,
re-use of inodes does not present a problem for qmail and is commonly
seen on UFS.
If you look at the log fragment carefully you'll see that the inode is
only reused after the message has been delivered and thus the file
deleted.
It would be a problem if the same inode was in use at the same time,
but the log fragment doesn't show that.
By way of an example, on a FreeBSD 4.2 UFS queue I see that the same
inode has been re-used over 100 times for some 1200 deliveries.
$ grep 'info msg' /var/log/qmail/current | cut -f4 -d' ' | cut -f1 -d: |
sort -n | uniq -c | sort -nr
177 8097707
165 8097716
118 8097715
83 8097913
75 8097709
71 8097768
62 8097947
48 8097699
42 8097909
33 8097990
29 8097701
23 8097755
16 8097879
16 8097769
15 8097910
14 8097943
14 8097914
14 8097712
13 8097719
11 8097753
10 8097998
10 8097997
8 8097984
...
Regards.
On Tue, Jul 24, 2001 at 01:45:57AM +0200, Lordy allegedly wrote:
> Hi Mike,
>
> this is a known issue with ReiserFS. As you might now, Ext2 and ReiserFS
> have many differences and you are just experiencing one of them. The whole
> problem is documented unter www.namesys.com (the homepage of ReiserFS)
> so you will find the information you need there.
>
> In general you have two options:
>
> 1) Moving the qMail partition back to ext2 (probably /var)
> 2) Patching qMail with the ReiserFS patch. (I think that one is available
> through
> a link on www.namesys.com too).
>
> Just for your information: I have a linux box running qMail and I have
> moved /home
> which contains the pop-boxes to ReiserFS but /var remains ext2. This makes sure
> that mail is "securely" stored once it is delivered and if your queue (or
> the partition)
> crashed you won't have much chances to restore it anyway.
>
> Hope this help,
> Lordy
>
> At 14:41 23.07.2001 -0600, you wrote:
> >Hello there.
> >I have been noticing slightly out of the ordinary things happening in my
> >qmail-send logs after changing the queue filesystem over to reiserfs.
> >I am seeing the same inode used for multiple messages. Is this normal?
> >
> >(other users email has been blanked, as has all senders. mine is known
> >to all of you, so why bother typing to cover mine eh? )
> >
> >excerpts from my qmail-queue log piped thru tai64nlocal
> >
> >2001-07-23 14:29:38.294512500 new msg 405006
> >2001-07-23 14:29:38.294529500 info msg 405006: bytes 2531 from
> ><[EMAIL PROTECTED]> qp 28395 uid 1016
> >2001-07-23 14:29:38.388694500 starting delivery 689: msg 405006 to local
> >vdomain-vuser@vdomain
> >2001-07-23 14:29:38.388713500 status: local 1/10 remote 0/20
> >2001-07-23 14:29:38.442249500 delivery 689: success:
> >POP_user_does_not_exist,_but_will_deliver_to_/users/catchall/dir/did_0+0+1/
> >2001-07-23 14:29:38.442273500 status: local 0/10 remote 0/20
> >2001-07-23 14:29:38.442278500 end msg 405006
> >2001-07-23 14:32:30.228899500 new msg 405006
> >2001-07-23 14:32:30.228916500 info msg 405006: bytes 4242 from
> ><[EMAIL PROTECTED]> qp 28405 uid 1016
> >2001-07-23 14:32:30.305868500 starting delivery 690: msg 405006 to local
> >[EMAIL PROTECTED]
> >2001-07-23 14:32:30.305886500 status: local 1/10 remote 0/20
> >2001-07-23 14:32:30.376295500 delivery 690: success: did_0+0+1/
> >2001-07-23 14:32:30.376313500 status: local 0/10 remote 0/20
> >2001-07-23 14:32:30.376319500 end msg 405006
> >2001-07-23 14:32:32.722033500 new msg 405006
> >2001-07-23 14:32:32.722049500 info msg 405006: bytes 1827 from
> ><[EMAIL PROTECTED]> qp 28409 uid 1016
> >2001-07-23 14:32:32.814920500 starting delivery 691: msg 405006 to local
> >[EMAIL PROTECTED]
> >2001-07-23 14:32:32.814937500 status: local 1/10 remote 0/20
> >2001-07-23 14:32:32.847071500 delivery 691: success: did_0+0+1/
> >2001-07-23 14:32:32.847089500 status: local 0/10 remote 0/20
> >2001-07-23 14:32:32.847094500 end msg 405006
> >
> >Mike
> >
> >--
> >Mike Hodson <[EMAIL PROTECTED]>
>
