Comment # 3 on bug 1032755 from Filipe Manana

(In reply to Jon Nelson from comment #2)
> (In reply to Filipe Manana from comment #1)
> > Can you please do the following?
> > 
> > 1) Report the kernel version. The btrfsprogs version is irrelevant, as all
> > it does is run the commands from the send stream (made by the kernel)
> > sequentially.
> 
> 4.4.49 and 4.4.57 and older versions, too.
> 
> 
> > 2) Provide the full output of the "btrfs receive -vvv ..." command.
> 
> 
> receiving snapshot snapshot uuid=074ed140-b5de-2b45-b411-c1b47e9328b4,
> ctransid=328695 parent_uuid=c2cc815d-dffa-2441-b363-ad8ffb1a3ecc,
> parent_ctransid=326104
> utimes root
> utimes usr
> utimes bin/cat
> utimes bin/cp
> utimes bin/gzip
> ...

Well, this really isn't the full output, is it? Judging those "..."...

> utimes etc/sysconfig/SuSEfirewall2.d/services/nfs-kernel-server
> utimes usr/share/man/man8/rpc.mountd.8.gz
> utimes usr/share/man/man8/rpc.nfsd.8.gz
> utimes var/lib/samba/private/msg.sock/1808
> utimes var/lib/samba/private/msg.sock/1891
> link root/.ssh/agent-turnip-pid19907 -> root/.ssh/agent-turnip
> link root/.ssh/agent-turnip-pid20340 -> root/.ssh/agent-turnip
> ERROR: link root/.ssh/agent-turnip-pid20340 -> root/.ssh/agent-turnip
> failed: File exists
> At snapshot snapshot

> 
> 
> 
> > 
> > 3) Ideally, provide an image of the filesystem (with btrfs-image) or the
> > output of btrfs-debug-tree. These would be very convenient but may not be
> > strictly necessary to debug and understand the problem.
> 
> That is one I'd really have to think about.

Take your time thinking about it. btrfs-image replaces the data with zeroes, so
all that you'll reveal is metadata (file names essentially).

thanks