DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=mRrBYUN50ziBelIV7LNUHAoZgU4VqgOPRf5wnQUTqhQ8Ws5QFif3V
	lsx/HxJQhVNZHscFOtrkgFoIuoYsAXyqhQxmq3nW4gdar1W8naEGgNUIhgYFYdT2
	dLqn+fSC9wXub+vJpiotvmjWvo0db4nwMvUGxGBcoOtsro2dFrSnXY=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 24 Apr 2014 18:45:32 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: rm -f behavior
Message-ID: <20140424164532.GV2339@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <5358260B.90807@obj-sys.com> <20140424142304.GT2339@calimero.vinschen.de> <53592F15.4040309@obj-sys.com> <20140424163624.GU2339@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="o0y1lerN6xYE2ROn"
Content-Disposition: inline
In-Reply-To: <20140424163624.GU2339@calimero.vinschen.de>
User-Agent: Mutt/1.5.21 (2010-09-15)

--o0y1lerN6xYE2ROn
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Apr 24 18:36, Corinna Vinschen wrote:
> On Apr 24 11:34, Douglas Coup wrote:
> > If I do "which rm" and "which chmod", it shows that both commands
> > resolve to the Cygwin binaries.
> >=20
> > The attached rm.notworking.trace file is from an "rm -f dac.txt"
> > command that gets the permission denied error; i.e., when the
> > permissions on the file are 444.  Things seem to start going south
> > at entry 34276.
>=20
> Gosh, how many ways to fail does transactional NTFS know?
>=20
> >    20   34002 [main] rm 7580 unlink_nt: Trying to delete \??\C:\mydocs\=
temp\dac.txt, isdir =3D 0
> >   274   34276 [main] rm 7580 unlink_nt: Opening \??\C:\mydocs\temp\dac.=
txt for removing R/O failed, status =3D 0xC0190052
>=20
> So you're getting a transaction error which isn't covered by the Cygwin
> DLL yet.  The error is STATUS_TRANSACTIONMANAGER_NOT_ONLINE.  Whatever
> this means.  How on earth can the TxF manager be "not online"?!?
> Unfortunately there's only very sparse information about this status
> code available.

Oh, btw., the associated Windows error code is 6719, and the english
error message is this:

  The object specified could not be created or opened, because its
  associated TransactionManager is not online.  The TransactionManager
  must be brought fully Online by calling RecoverTransactionManager to
  recover to the end of its LogFile before objects in its Transaction or
  ResourceManager namespaces can be opened.  In addition, errors in
  writing records to its LogFile can cause a TransactionManager to go
  offline.

> Before I make any changes to Cygwin, I'll try to get some info from
> the Microsoft side of things...

http://social.msdn.microsoft.com/Forums/en-US/11bfd4ca-f7b7-45cd-a3bc-2ebce=
60b734c/


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--o0y1lerN6xYE2ROn
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTWT+sAAoJEPU2Bp2uRE+goQUP/292tRvWVNlECfLhyXOOON5E
FseFvd1juyV1/hwquv9fg/MUqEpxOPwbmImpm+fw78Y8E0hNQcXEmvaZ78Zqp5G4
TlrmDqAIk2ldiok3hZN1Kb1+DKyHzwhUjkFADNcj97cJPqOixZFYh8+KnlpDDRhU
Ee6OH1/EDKzw00eDNFZQpcmNRW44QTY3CZ0Cw+TpyuEc7C8EcgVpHxZPq577KhDn
XRkPNiaz93hpDhtJdkL6wW8ZpmcL3nfPnJKxMxoQ4i2COvVDP0GyXFJVEkSmyZGa
xVJ6ZwpVep3+qdouu8ynlEGdgDOvLay6ASzY1/a1aSutD42RA4KmQGpRJSrrIvJ5
XHckYkHER4Xu2Oh37d9hv/usJH8Y0b+Xj8MeIpXdHYaO2kIqQprT9fgTlHcJnSnV
Z4rBri7YJfds8wPpQrmbbnfPNLpSC20xwUjjLr3d6pBOo6mEMg5cnjyIUE+hq9UV
LLjXO0PzNrXRcIHj4hBRI0636fR2S0UGCWJTBAyFHu4zS/HJWrP6BBfYTzKl18ZO
S/RoP6TnR7G9IEURxUdEb633SVNieXL9quqi3AO+i0W8AvlRzGKqTHWpXyyP1VZO
pNzHzwEQN2NxQewUddXs3OuluNSeNXvihYzeM6n/czwlB+ZqrVOht824rYUJB7UY
xTRvAC1HvpuGuxFdp8f7
=o231
-----END PGP SIGNATURE-----

--o0y1lerN6xYE2ROn--