pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
On-line backup - /bin/tar:  Error exit delayed from previous errors
5+ messages / 3 participants
[nested] [flat]

* On-line backup - /bin/tar:  Error exit delayed from previous errors
@ 2006-08-02 12:53  Mr. Dan <bitsandbytes88@hotmail.com>
  0 siblings, 1 reply; 5+ messages in thread

From: Mr. Dan @ 2006-08-02 12:53 UTC (permalink / raw)
  To: pgsql-admin

/bin/tar: /sqldata/Linux.pgsql/base/19473856/19524666: file changed as we 
read it

Hi,

I'm seeing that a file changed during the /bin/tar process.  Is that 
anything to be concerned about?
This is the first time this happened in a month.  Does that mean I'm still 
backed up in regards to that database?  I'm using v810 here.

The tar file exists, so the tar file was created.

Thanks,
~DjK





^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: On-line backup - /bin/tar:  Error exit delayed from
@ 2006-08-02 13:46  Bruce Momjian <bruce@momjian.us>
  parent: Mr. Dan <bitsandbytes88@hotmail.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Bruce Momjian @ 2006-08-02 13:46 UTC (permalink / raw)
  To: Mr. Dan <bitsandbytes88@hotmail.com>; +Cc: pgsql-admin

Mr. Dan wrote:
> /bin/tar: /sqldata/Linux.pgsql/base/19473856/19524666: file changed as we 
> read it
> 
> Hi,
> 
> I'm seeing that a file changed during the /bin/tar process.  Is that 
> anything to be concerned about?
> This is the first time this happened in a month.  Does that mean I'm still 
> backed up in regards to that database?  I'm using v810 here.
> 
> The tar file exists, so the tar file was created.

The error is expected.  The WAL files archived will correct any changes
in the backup.

-- 
  Bruce Momjian   bruce@momjian.us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: On-line backup - /bin/tar: Error exit delayed from previous errors
@ 2006-08-03 13:13  Mr. Dan <bitsandbytes88@hotmail.com>
  1 sibling, 0 replies; 5+ messages in thread

From: Mr. Dan @ 2006-08-03 13:13 UTC (permalink / raw)
  To: marco.bizzarri@gmail.com; pgsql-admin


Hi Marco/all,

Thanks for the response.  I've been running the same online-backup commands 
for over a year and restores have always worked fine.  I've never seen 'file 
changed as we read it' though,  before yesterday.  The database is new to 
the server, as of a week.  So, I'm more inclined to think it's somehting 
going on with the database instead of  the command to do the backup.  BTW, I 
received the same message this morning.  So, 2 days in a row (no pun 
intended) on the same database and the same second number following the 
databe number.
/bin/tar: /sqldata/Linux.pgsql/base/19473856/19524666: file changed as we 
read it

psql -d DBN -c "SELECT pg_start_backup('somehting.backup');"
tar -zcvf /something.tar.gz /PGDATA/dir/*
psql -d DBN -c "SELECT pg_stop_backup();"

Thanks,
~DjK






>From: "Marco Bizzarri" <marco.bizzarri@gmail.com>
>To: "Mr. Dan" <bitsandbytes88@hotmail.com>
>Subject: Re: [ADMIN] On-line backup - /bin/tar: Error exit delayed from 
>previous errors
>Date: Thu, 3 Aug 2006 10:02:25 +0200
>
>I think you should post the command you're using, as well as the
>condition in which you're doing the tar: is the postgresql running or
>not?
>
>IMHO, I would be *VERY* concerned about such a message.
>
>Regards
>Marco
>
>On 8/2/06, Mr. Dan <bitsandbytes88@hotmail.com> wrote:
>>/bin/tar: /sqldata/Linux.pgsql/base/19473856/19524666: file changed as we
>>read it
>>
>>Hi,
>>
>>I'm seeing that a file changed during the /bin/tar process.  Is that
>>anything to be concerned about?
>>This is the first time this happened in a month.  Does that mean I'm still
>>backed up in regards to that database?  I'm using v810 here.
>>
>>The tar file exists, so the tar file was created.
>>
>>Thanks,
>>~DjK
>>
>>
>>
>>---------------------------(end of broadcast)---------------------------
>>TIP 9: In versions below 8.0, the planner will ignore your desire to
>>        choose an index scan if your joining column's datatypes do not
>>        match
>>
>
>
>--
>Marco Bizzarri
>http://notenotturne.blogspot.com/





^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: On-line backup - /bin/tar: Error exit delayed from previous errors
@ 2006-08-03 14:25  Mr. Dan <bitsandbytes88@hotmail.com>
  1 sibling, 1 reply; 5+ messages in thread

From: Mr. Dan @ 2006-08-03 14:25 UTC (permalink / raw)
  To: pgsql-admin


Another thing that conerns me is that the zipped file size keeps changing.
I'm backing up 10GB total.  One night the backup file was 9 GB, one night it 
was 874 MB and just now, 5 GB.   I'm expecting a file around 1.5 GB (15% of 
the 10GB) that's there.





^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: On-line backup - /bin/tar: Error exit delayed from previous
@ 2006-08-03 18:59  Andy Shellam <andy.shellam-lists@mailnetwork.co.uk>
  parent: Mr. Dan <bitsandbytes88@hotmail.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Andy Shellam @ 2006-08-03 18:59 UTC (permalink / raw)
  To: Mr. Dan <bitsandbytes88@hotmail.com>; +Cc: pgsql-admin

We occasionally get the "file changed while being read" error, usually 
only once or twice a month (and we run nightly backups.)  It's nothing 
to be concerned about, as someone else mentioned, the WAL logs will fix 
any internal inconsistencies.

Regarding the file sizes, because it's zipped (I believe) the 
compression ratios can change depending on the contents of the files, 
hence the differences in size, but I wouldn't have thought it be that 
drastic.

Thing I would do, is on a spare machine (or same one if you've got the 
space), unzip three of the files that are different sizes (e.g. 874MB, 
5GB, 9GB) and then compare the sizes of the unzipped data.  If it 
differs greatly in the same fashion, you've got a problem.

Also just double check you're not backing up WAL logs as well (i.e. 
excluding pg_xlog.)

Andy.

Mr. Dan wrote:
>
> Another thing that conerns me is that the zipped file size keeps 
> changing.
> I'm backing up 10GB total.  One night the backup file was 9 GB, one 
> night it was 874 MB and just now, 5 GB.   I'm expecting a file around 
> 1.5 GB (15% of the 10GB) that's there.
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>
> !DSPAM:37,44d207ac143291676420085!
>
>




^ permalink  raw  reply  [nested|flat] 5+ messages in thread


end of thread, other threads:[~2006-08-03 18:59 UTC | newest]

Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-08-02 12:53 On-line backup - /bin/tar:  Error exit delayed from previous errors Mr. Dan <bitsandbytes88@hotmail.com>
2006-08-02 13:46 ` Re: On-line backup - /bin/tar:  Error exit delayed from Bruce Momjian <bruce@momjian.us>
2006-08-03 13:13 ` Re: On-line backup - /bin/tar: Error exit delayed from previous errors Mr. Dan <bitsandbytes88@hotmail.com>
2006-08-03 14:25 ` Re: On-line backup - /bin/tar: Error exit delayed from previous errors Mr. Dan <bitsandbytes88@hotmail.com>
2006-08-03 18:59   ` Re: On-line backup - /bin/tar: Error exit delayed from previous Andy Shellam <andy.shellam-lists@mailnetwork.co.uk>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox