Hi,
We are facing issues while backing up our 1205 GB filesystem on LTO5 Tape. During backup the "backup: The lseek call failed." messages were generated, I want to know why these messages were generating
AIX version is: 6100-08-00-0000
backup: The date of this level 0 backup is Mon Mar 11 14:57:59 GMT+05:00 2013.
backup: The date of the last level 0 backup is the epoch.
backup: Backing up /dev/rfslv04 (/backup2) to /dev/rmt0.
backup: 0511-251 The file system is still mounted; data may not be consistent.
Use the umount command to unmount the filesystem; then do the backup.
backup: Mapping regular files. This is Pass 1.
backup: Mapping directories. This is Pass 2.
backup: There are an estimated 1397889184 1k blocks.
backup: Backing up directories. This is Pass 3.
backup: The lseek call failed.
backup: Backing up regular files. This is Pass 4.
backup: The lseek call failed.
backup: The lseek call failed.
backup: The lseek call failed.
backup: The lseek call failed.
backup: The lseek call failed.
backup: The lseek call failed.
backup: The lseek call failed.
backup: The lseek call failed.
backup: The lseek call failed.
backup: The lseek call failed.
backup: The lseek call failed.
backup: The lseek call failed.
backup: The lseek call failed.
backup: The lseek call failed.
backup: The lseek call failed.
backup: There are 1264566843 1k blocks on 1 volumes.
backup: The tape is rewinding.
backup: The backup is complete.
1) AIX version is: 6100-08-00-0000 is the DVD release. You should update to a SP.
2) Get the SP files using smit suma or FixCentral, download .
3) Once you have the downloads, smitty update_all .
Lastly, why are you using backup (i.e., backup by inode) rather than backupbyfilename.
Usually backups are by filename and/or made for a whole volume group.
# savevg -i -f /dev/rmt0 vgName
or
# cd /some/directory; find . | backup -if /dev/rmt0
In your case it looks like the last option would be:
# cd /backup; find . | backup -if /dev/rmt0
Note also, if doing backup by inode - as your example - you should unmount /backup first
Example (where I write to a file, not a tape)
michael@x054:[/home/michael]umount /audit
michael@x054:[/home/michael]backup -0 -f /data/backups/audit.backup /audit
backup: The date of this level 0 backup is Tue Mar 19 13:30:21 CUT 2013.
backup: The date of the last level 0 backup is the epoch.
backup: Backing up /dev/rhd12audit (/audit) to /data/backups/audit.backup.
backup: Mapping regular files. This is Pass 1.
backup: Mapping directories. This is Pass 2.
backup: There are an estimated 1183 1k blocks.
backup: Backing up directories. This is Pass 3.
backup: Backing up regular files. This is Pass 4.
backup: There are 1147 1k blocks on 1 volumes.
backup: The backup is complete
If you continue to have these lseek errors, file a call with IBM or your BP for support and diagnosis.
1 Like
Thanks Michael
We are using the find /backup | backup -ivf /dev/rmt0 command to backup our filesystem however the AIX level was at base level without SP which is now updated to 6100-08-02-1316 . I will take the backup again and contact IBM if the problem still persist.
Hope that solves it for you. However, in your example you were not doing backupbyname .
This information:
backup: The date of this level 0 backup is Mon Mar 11 14:57:59 GMT+05:00 2013.
backup: The date of the last level 0 backup is the epoch.
backup: Backing up /dev/rfslv04 (/backup2) to /dev/rmt0.
Only occurs with backupbyinode .
If your intent is backupbyname you will also need to verify your script.
Hope this helps!
Yes Michael you are correct. Actually I was only looking at logs which is echoing that backup is going by filename backup -ivf /dev/rmt0 command, but when I go through the script I found that backup is going with backup -f'/dev/rmt0' -'0' '-U' command. Now I have modified the script & taking the backup again and let me check whether this change will resolve the lseek failed errors or not.
Thanks again.