[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <200612180106_MC3-1-D56B-FD2F@compuserve.com>
Date: Mon, 18 Dec 2006 01:03:08 -0500
From: Chuck Ebbert <76306.1226@...puserve.com>
To: linux-kernel <linux-kernel@...r.kernel.org>
Cc: linux-cifs-client <linux-cifs-client@...ts.samba.org>,
Steve French <sfrench@...ba.org>, Andrew Morton <akpm@...l.org>
Subject: 2.6.19.1 bug? tar: file changed as we read it
Trying to backup up a filesystem mounted via CIFS, I got these messages
from tar:
tar: t/2.6.10-orig/net/ipv4/netfilter/ipt_CONNMARK.c: File shrank by 1178 bytes; padding with zeros
tar: t/2.6.10-orig/net/ipv4/netfilter/ipt_TCPMSS.c: File shrank by 4177 bytes; padding with zeros
tar: t/2.6.10-orig/net/ipv4/netfilter/ipt_DSCP.c: File shrank by 1172 bytes; padding with zeros
tar: t/2.6.10-orig/net/ipv4/netfilter/ipt_tos.c: file changed as we read it
tar: t/2.6.10-orig/net/ipv4/netfilter/ipt_ECN.c: File shrank by 1638 bytes; padding with zeros
tar: t/2.6.10-orig/net/ipv4/netfilter/ipt_mark.c: file changed as we read it
tar: t/2.6.10-orig/net/ipv6/netfilter/ip6t_mark.c: file changed as we read it
This was with kernel 2.6.19.1 SMP on x86_64, creating a tar file on a local
jfs filesystem (t is the source path on a cifs mount.)
Using 2.6.18.6-pre2 uniprocessor i386, with smbfs instead of cifs, everything
works fine so I'm pretty sure the server is OK.
Does this match any known problems?
--
MBTI: IXTP
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists