Version: 2.6.8-16sarge5
On Tue, Sep 26, 2006 at 12:08:14PM +0200, Peter Kruse wrote:
> Hello,
>
> it looks like that the latest security update to the kernel fixes this
> problem:
Thanks, closing therefore.
--
dann frazier
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "un
Hello,
it looks like that the latest security update to the kernel fixes this
problem:
http://www.debian.org/security/2006/dsa-1184
here:
http://bugzilla.kernel.org/show_bug.cgi?id=6828
and here:
http://www.securityfocus.com/bid/19396/info
Best.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTE
"Peter Kruse" <[EMAIL PROTECTED]> writes:
> Hello Goswin,
>
>
> On 6/16/06, Goswin von Brederlow <[EMAIL PROTECTED]> wrote:
> I noticed this and can reproduce it by running exportfs -u,
> umount,
> resize2fs, mount, exportfs and then accessing some previously used
> file o
Hello Goswin,On 6/16/06, Goswin von Brederlow <[EMAIL PROTECTED]> wrote:
Did you reboot the nfs server while clients had the fs mounted? Orstoped the nfsd and run fsck or a resize? Anything that could change
the inode numbers without the clients getting any notice?Yes, we rebooted and recreated the
"Peter Kruse" <[EMAIL PROTECTED]> writes:
> Hello,
> at the moment our server prints regularily like two times a minute the same
> message to kern.log:
> EXT2-fs error (device dm-5): ext2_get_inode: bad inode number: 30130240
> I checked and the inode really does not exist on the specified device
Hello,at the moment our server prints regularily like two times a minute the same message to kern.log:EXT2-fs error (device dm-5): ext2_get_inode: bad inode number: 30130240I checked and the inode really does not exist on the specified device (dm-5 is
the device with minor number 5 under /dev/mappe
6 matches
Mail list logo
