public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@argo.co.il>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	linux-cifs-client <linux-cifs-client@lists.samba.org>,
	Steve French <sfrench@samba.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.19.1 bug?  tar: file changed as we read it
Date: Mon, 18 Dec 2006 09:17:32 +0200	[thread overview]
Message-ID: <4586408C.2050408@argo.co.il> (raw)
In-Reply-To: <200612180106_MC3-1-D56B-FD2F@compuserve.com>

Chuck Ebbert wrote:
> 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?
>   

In 2.6.20-rc1, some of these files have other files with the same name 
in the same directory (modulo case).  Perhaps this is confusing cifs.

Can you check where all of the files in your case share that property?

example:

    [avi@firebolt linux-2.6]$ find net -iname ipt_tos.c
    net/ipv4/netfilter/ipt_TOS.c
    net/ipv4/netfilter/ipt_tos.c

    [avi@firebolt linux-2.6]$ find net -iname ipt_ecn.c
    net/ipv4/netfilter/ipt_ECN.c
    net/ipv4/netfilter/ipt_ecn.c


-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  reply	other threads:[~2006-12-18  7:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-18  6:03 2.6.19.1 bug? tar: file changed as we read it Chuck Ebbert
2006-12-18  7:17 ` Avi Kivity [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-12-18 16:13 Chuck Ebbert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4586408C.2050408@argo.co.il \
    --to=avi@argo.co.il \
    --cc=76306.1226@compuserve.com \
    --cc=akpm@osdl.org \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfrench@samba.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox