-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Running the FD with debug level 400 might help to see if it generates the SHA1
at all.
Here's the data for the broken file:
gundabad-fd: find_one.c:357-32 File :
/usr/share/postgresql-8.4/man/man7/table.7.bz2
gundabad-fd: backup.c:326-32
On Mon, 19 Jul 2010 15:44:00 +0200, Andreas Koch said:
I'll make another attempt at interpreting the data:
The broken file is a hard-link (to
/usr/share/postgresql-8.4/man/man7/with.7.bz2). The crypto_digest is only
calculated for the regular file
On Thu, 08 Jul 2010 18:19:49 +0200, Andreas Koch said:
with FI=137 occuring in the two log lines
gundabad-dir: catreq.c:407-25 UpdCat VolSessId=12 VolSessT=1277829932 FI=137
Strm=1 data_len=123
...
gundabad-dir: catreq.c:407-25 UpdCat VolSessId=12 VolSessT=1277829932 FI=137
Strm=10
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/05/2010 09:19 PM, Martin Simmons wrote:
On Mon, 05 Jul 2010 17:54:29 +0200, Andreas Koch said:
I used the wrong JobID, those were indeed the rows for the differential
backup. The data for the underlying full is attached below. It does lack a
On 07/02/2010 04:52 PM, Martin Simmons wrote:
It would be interesting to check the MD5 column in the output of the SQL query
SELECT Path.Path,Filename.Name,File.MD5 FROM File,Filename,Path WHERE
File.JobId=
AND Filename.FilenameId=File.FilenameId
AND Path.PathId=File.PathId ORDER BY
On Mon, 05 Jul 2010 13:10:17 +0200, Andreas Koch said:
On 07/02/2010 04:52 PM, Martin Simmons wrote:
It would be interesting to check the MD5 column in the output of the SQL
query
SELECT Path.Path,Filename.Name,File.MD5 FROM File,Filename,Path WHERE
File.JobId=
AND
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/05/2010 03:50 PM, Martin Simmons wrote:
On Mon, 05 Jul 2010 13:10:17 +0200, Andreas Koch said:
On 07/02/2010 04:52 PM, Martin Simmons wrote:
It would be interesting to check the MD5 column in the output of the SQL
query
SELECT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/05/2010 03:50 PM, Martin Simmons wrote:
On Mon, 05 Jul 2010 13:10:17 +0200, Andreas Koch said:
Are those definitely the rows for the Full backup? I'm a little surprised to
see I_AM_FAKE_AHK_3.
I used the wrong JobID, those were indeed the
On Mon, 05 Jul 2010 17:54:29 +0200, Andreas Koch said:
I used the wrong JobID, those were indeed the rows for the differential
backup. The data for the underlying full is attached below. It does lack a
checksum for table.7.bz2.
OK, so that explains the warning.
Now the mystery is why it
On Thu, 01 Jul 2010 17:15:09 +0200, Andreas Koch said:
On 07/01/2010 02:37 PM, Martin Simmons wrote:
Does the FileSet have just one Include section and one Options section?
If
it is more complicated than that, please post it.
The complete FileSet is:
# List of files to be
On 06/30/2010 12:55 PM, Martin Simmons wrote:
On Tue, 29 Jun 2010 18:06:41 +0200, Andreas Koch said:
Can no one help with this? I'm somewhat worried that the many lines of
Warning: Can't verify checksum for (filename...)
during backup indicate a configuration problem and I fear for the
On Thu, 01 Jul 2010 13:10:38 +0200, Andreas Koch said:
On 06/30/2010 12:55 PM, Martin Simmons wrote:
On Tue, 29 Jun 2010 18:06:41 +0200, Andreas Koch said:
Can no one help with this? I'm somewhat worried that the many lines of
Warning: Can't verify checksum for (filename...)
Hello Andreas,
Have you checked the drive?
Try copying the files to another location and see if the copies give
the same error.
JBB
Thursday, July 1, 2010, 7:10:38 AM, you wrote:
On 06/30/2010 12:55 PM, Martin Simmons wrote:
On Tue, 29 Jun 2010 18:06:41 +0200, Andreas Koch said:
Can
On 07/01/2010 01:17 PM, Jonathan B Bayer wrote:
Hello Andreas,
Have you checked the drive?
The drive is a RAID-5 volume on an 8-disk Adaptec 5805 controller.
Try copying the files to another location and see if the copies give
the same error.
By copies you just mean cp, right? If so: No
On Tue, 29 Jun 2010 18:06:41 +0200, Andreas Koch said:
Can no one help with this? I'm somewhat worried that the many lines of
Warning: Can't verify checksum for (filename...)
during backup indicate a configuration problem and I fear for the consistency
of our data.
The warning
Can no one help with this? I'm somewhat worried that the many lines of
Warning: Can't verify checksum for (filename...)
during backup indicate a configuration problem and I fear for the consistency
of our data.
Any hints would be appreciated,
Andreas Koch
On 06/21/2010 01:41 PM,
16 matches
Mail list logo
