Re: dealing with timestamp (in-)accuracy

--===============1006421224==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="sDKAb4OeUBrWWL6P"
Content-Disposition: inline


--sDKAb4OeUBrWWL6P
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Message by -Les Mikesell- from Tue 2008-03-11:
> Lasse Kliemann wrote:
>>>
>>> Did you actually see missing files in incrementals?
>>
>> Yes. Please try the attached script. It will report FAIL with, I guess,=
=20
>> 95% probability, meaning that the file called `1' is not included in the=
=20
>> level one dump. When you insert a sleep statement at the place marked=20
>> HERE, the error probability decreases. With 1 second of sleep, I could n=
ot=20
>> provoke an error. With 0.9 seconds, it still might happen.
>>
>> It does not help to put sleep or sync statements between the touch=20
>> statement and the dump.
>
> I thought the problem with direct dump-like access to a live filesystem  =
=20
> had been known for ages: http://dump.sourceforge.net/isdumpdeprecated.html

It's the same here (on Linux) for filesystems that are not live, but mounte=
d=20
read-only. The test setup is just more complicated then, and one needs root.

Also, wouldn't it be enough here to simply have no modifications done to th=
e=20
directory (called `src' in my test script) during the dump?

Oh, and how could an instable filesystem explain why a sleep *after* the du=
mp=20
corrects the problem, and not a sleep or a sync *before* the dump?

Lasse

--sDKAb4OeUBrWWL6P
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (GNU/Linux)

iQIcBAEBAgAGBQJH1rjvAAoJEFYll6N4nhdv48IP/2JdWhSxZaO1S/4w+E/R6CwB
ckdcSkyqKJAch8qjMvDpbL6KlI3FiBLJ5u9OFAwVL1V0kWzrAu3uQj9uV+KixicX
7q+7iTYn2fIvHV6opN7886F29pbQBfI890Ssp+jAt0GcWmgc4tOsupEelUMOMetw
bxDEvE1z8RuY9rH3bmD73jIzsKbB1D+7x8hlFzfOM1d7H26q3a+31p28WOZum69V
6jzEiOpJDdxIyeTIBP93+jGMCosYdBaZDqPGYBoZvsfAYfeGJn2LWsSowzTky901
3YGEtY6NbUNO59DFc028jCNWS9eZXByRLp5/Wqx+F8r26QXPaR+RCP5G0KB9YBcM
8MSQRiTuP2YdmCCE32tiucVc96ipiChf8G5GjTOA7L2Qdb0xJy0teQ00JPgxXcjm
U2rLqhsA6n0O6yRkpzeFPAOCIppu1tHabGZBJVrDxk21V3RAmBR164gjNtZ9kJde
AxFMuqqisT7JVNfmplnclI/r3V89y+9X88j3Y/xN6VzoSJDft2XTneXQA2b0INzy
AZxLzZojKFtSY928FD345/XD9pS2jsxHuNXzbJvC+vJI6ANpEOmBxuAsRaSgor4L
SYr26XxBXeqNz4N5PCqqEURn61zKqTFYOaE3NoK6eCmazVcPvoWYa+7bBZMKIUrD
pIr42Wn99pS0L8aZzdgP
=Eesc
-----END PGP SIGNATURE-----

--sDKAb4OeUBrWWL6P--

--===============1006421224==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Star-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/star-users

--===============1006421224==--