X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 8A1853844044
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1623894568;
	bh=30q4YO9LOfP3cw99joprZ4v+gasMWjPzIIRW0wvABXA=;
	h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	From;
	b=gf66SJhj5ghL1O/hh4AWKmstyspV9cuUgjOx+I3XkLF5w9HXoJTS2G0MAlGJh6Yw0
	UfZKV3bbDzxwHCHuZsTJJLzLZKroKDzbk5M9ghSZSkdUcVJpbcdoHGxXPZgCw3iJR+
	CsNvOuQ+o+R6OD6CIFdc9KvZ0Po32RpAcyprmpb8=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.1 sourceware.org C1B66384802E
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:cc;
	bh=KQ3x3Yxi4U457THXxeAAo0TxEQ2nMcoMU2K1JesaCjQ=;
	b=Rh/9PNmo0g2fgmJ7nFl9SUk6s1oRXERaTt8FdayqKTQ/p+Ebr7DUWxhTdb2+wMS+8q
	c2wPohx4Wy1mQZCQAUwKfloc4n6Gb0ueWkEN8YZv7cm7cH3lk4cWfIVhkpzHM7aVy4PL
	HgdY/7yBjCkmBlxMFDddW89ZuEdIBoBsGYnTafBwdklfWCe93/tY23GzRt59L9DVy82H
	/lm/n3+gHi504KgJVCOrKKCDsZ8cGr/1OsHqv7bAXa5ZBBwcJF9t2AgZLH+5k0XzndpC
	Ih1MM0FNC/4gt1QzU19k4tWchRq1D1y+xk6A0CODlRZeZzErjd3sf2d04KEPf8YmnMLl
	WfWw==
X-Gm-Message-State:	AOAM531M2EfEeWc3PCEsIsDmC+/G3tqFBZE/Oveh5hi1kVVXYnAhTruU
	pg3G2/myl/B3iIHTiAMqLk0oV2H69Eu8bb0iMRQ=
X-Google-Smtp-Source:	ABdhPJys7EDGplLwtRpCEttjyubKhtOtfWFaskR7JrjIjAjnY/WIYuVA049ayH1U0cKSwZex68GoQqgw4ZOzhNuKoSw=
X-Received:	by 2002:aca:4c85:: with SMTP id z127mr1547077oia.21.1623894472874;
	Wed, 16 Jun 2021 18:47:52 -0700 (PDT)
MIME-Version:	1.0
References:	<60C82AAB DOT 1090901 AT tlinx DOT org>
	<CANV2+nUOP4eyReRK-RJ1mUrs7ZHNUnKsgWi_eVNJKjhPjZfjzA AT mail DOT gmail DOT com>
	<60C917DD DOT 1070403 AT tlinx DOT org>
In-Reply-To:	<60C917DD.1070403@tlinx.org>
Date:	Wed, 16 Jun 2021 18:47:40 -0700
Message-ID:	<CANV2+nWW-8GefJJYS9pxsGEa2LjwEnX+e16auMScYStqZdqODA@mail.gmail.com>
Subject:	Re: bug in cygwin tar reading unexpected input(s)...
To:	L A Walsh <cygwin AT tlinx DOT org>
X-Spam-Status:	No, score=-1.9 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE,
	RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS,
	TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-Content-Filtered-By:	Mailman/MimeDel 2.1.29
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Russell VT via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Russell VT <russellvt AT gmail DOT com>
Cc:	cygwin <cygwin AT cygwin DOT com>
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

Replay by from my phone, so it's a bit brief...

Try opening a Cygwin terminal AS administrator, making sure it gives you
the "process may modify the system" warning dialog, etc... Then repeat

If it works, or complains less, then the problem is permissions at *some*
level.

Despite Windows having "administrator" type groups, they are STILL
protected parts of the filesystem, etc. There will be fewer protections by
using the "system" account, etc.

WARNING: Using this account MAY produce irreparable harm to the system. Do
this at your own risk.

-- 
Russell M. Van Tassell
russellvt AT gmail DOT com

This message was sent from my wireless handheld device.

On Tue, Jun 15, 2021, 14:14 L A Walsh <cygwin AT tlinx DOT org> wrote:

>
>
> On 2021/06/15 00:16, Russell VT wrote:
> > I think we need more context, here... as what does Windows versus Cygwin
> > think those permissions are...???
> ---
>         Which permissions?  The error is 'no such object', not
> 'access denied'.  I believe it is similar to trying to read (or
> modify) xattr's or acl's on linux symlinks.
>
> >
> > Are you running your terminal, as you... or did you run it as
> Administrator?
> ---
>         I am in group Administrators as well as Domain Admins
> (Samba Domain).  Domain Admins and System are both in the
> local Administrators group.
>
>
> > Have you run an update, and not rebooted?
> ---
>         I don't believe so at that time, but I have rebooted since then.
> The problem only occurred on files that were symlinks as seen by Windows
> and Cygwin.
> >
> > There should be some "basic shell debugging" done here, first...
> ---
>         I'm not sure what you mean.  Oops, I forgot to list the
> command line, but thought that "--xattrs" might be implied from the
> fact that the error was about retrieving xattrs.
>
>         Cmdline was using shell script calling a function, "backup_dir"
> with "ProgramData" from the root directory, where the function was:
>
> backup_dir() {
>   my DIR=${1:?}
>   tar c --acls --xattrs --sparse -b 2048 --one-file-system "$DIR" |
>     dd bs=1M iflag=fullblock of="/b/June_backups/$DIR" oflag=nonblock
> }
>
>
> > since
> > there's a disconnect from when tar gets its file list, and when it
> > physically goes to retrieve a (possibly temporary) file. It will also
> > complain about directories it can read, but not access.
> ---
>         Those were symlinks, not directories.
> > So, it would be
> > better to figure out what the "difference" is between what you expect,
> > and what actually happened with the tar.
> ---
>         I would expect it might not complain about not being
> able to read xattr's on symlinks?  I don't think it complains about
> not being able to read them on linux -- or at least I've never seen
> such.
>
> > Unfortunately, permission issues between Windows and Cygwin can be
> > */extremely/* complex (ie. there are a ton of details missing here,
> > which might make it easier to help troubleshoot).
> ---
>         What necessary details are missing?
>
> >
> > Hope that helps point you in a good direction.
> ---
>         Not sure. I thought I was reporting a bug in cygwin tar
> giving an error about trying to read xattrs on symlinks, as I don't
> believe it gives an error on linux doing the same thing.  Does it?
> Thanks for your questions, but I'm still not very clear on what
> I left out.
>
>         I'd tend to ignore the error on what appeared to be
> a misspelled filename, as I'm not even sure how to recreate
> that file, but attempting to dump xattrs on a symlink seems like
> a pretty straight forward symptom/testcase.  What more details
> do you think would be pertinent?
>
> Thanks!
> -Linda
>
>
> >
> > Cheers!
> > Russell VT
> >
> > On Mon, Jun 14, 2021 at 9:22 PM L A Walsh <cygwin AT tlinx DOT org
> > <mailto:cygwin AT tlinx DOT org>> wrote:
> >
> >     Tar'ing up a windows dir (ProgData) had some unexected failures:
> >
> >     Several of the sort:
> >
> >     tar: Dbgview: Warning: Cannot llistxattrat: No such file or directory
> >     tar: Desktops: Warning: Cannot llistxattrat: No such file or
> directory
> >     tar: DiskView: Warning: Cannot llistxattrat: No such file or
> directory
> >     tar: LoadOrd: Warning: Cannot llistxattrat: No such file or directory
> >     tar: portmon: Warning: Cannot llistxattrat: No such file or directory
> >
> >     Where the item listed (Dbgview, DiskView, etc) is a
> >     windows symlink like:
> >
> >     2019/02/07  22:53    <SYMLINK>      Dbgview [SI\Dbgview.exe]
> >     2019/02/07  22:53    <SYMLINK>      Desktops [SI\Desktops.exe]
> >     2019/02/07  22:53    <SYMLINK>      DiskView [SI\DiskView.exe]
> >
> >     and stems from the use of the --xattrs switch.
> >
> >     Win7SP1x64
> >     cygcheck (cygwin) 3.2.0
> >
> >     The tar continued and finished much as it would after an unreadable
> >     file.
> >
> >     Another error, maybe similar,
> >
> >
> >     tar: C\:Prog64FastPictureViewer: Warning: Cannot file_has_acl_at: No
> >     such file or directory
> >
> >      From a file in "C:\Program Files\FastPictureViewer" [likely
> mis-]named
> >     "C:Prog64FastPictureViewer"
> >
> >     It seems to be a .dll, that somehow got its name mangled.
> >
> >     Not sure what it was trying to do, but the file seems to be 'in-use'.
> >
> >
> > --
> > Russell M. Van Tassell <russellvt AT gmail DOT com <mailto:russellvt AT gmail DOT com
> >>
>

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -