WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: backup/restore error  (Read 2483 times)

Offline xpto09

  • WikiUser
  • *
  • Posts: 30
backup/restore error
« on: July 25, 2009, 06:27:08 PM »

I boot with the following options:
tinycore tce=hda1 restore=hda1

I installed firefox, mplayer and I got to make backup.
Now, there is this warning:

Backup produced erros.
Please see /tmp/backup_status.
Shutdown Aborted!

tc@box:/tmp$ cat backup_status
tar: removing leading '/' from member names

There is the message in the boot:
Ext3.fs: No journal found

dmesg:
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
EXT3-fs: no journal found.
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended ****I ran e2fsck****
EXT3 FS on hdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
EXT3-fs: no journal found.
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on hdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
squashfs: version 4.0 (2009/01/31) Phillip Lougher
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
eth0: link up, 100Mbps, full-duplex
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 9
PCI: setting IRQ 9 as level-triggered
oss_ich 0000:00:05.0: PCI INT A -> Link[LNKA] -> GSI 9 (level, low) -> IRQ 9
usbcore: registered new interface driver oss_usb
mtrr: base(0xe0000000) is not aligned on a size(0x1c00000) boundary
mtrr: no MTRR for e0000000,1c00000 found
mtrr: base(0xe0000000) is not aligned on a size(0x1c00000) boundary

Offline ^thehatsrule^

  • Administrator
  • Hero Member
  • *****
  • Posts: 1726
Re: backup/restore error
« Reply #1 on: July 25, 2009, 06:49:50 PM »
Most likely your /opt/.filetool.lst is bad.  Essentially, there should not be any /'s in the beginning of any line.

Offline xpto09

  • WikiUser
  • *
  • Posts: 30
Re: backup/restore error
« Reply #2 on: July 25, 2009, 07:00:44 PM »
Most likely your /opt/.filetool.lst is bad.  Essentially, there should not be any /'s in the beginning of any line.

There was the line:
/usr/lib/codecs

Now:
usr/lib/codecs

And the backup work!

Offline samedirection

  • Jr. Member
  • **
  • Posts: 64
Re: backup/restore error
« Reply #3 on: July 25, 2009, 11:10:26 PM »
I've had the wont-backup-because-of-slashes-in-/opt/.filetool.lst problem, too.  It's a pesky one.  I wonder if either the .filetool.lst file could take a comment reminding people to insert the files without initial slashes, or the backup script could be made to just ignore (or strip) initial slashes.  At the moment it is a case of 'making the user do what the computer needs' rather than making the computer to do what the user might expect. 

(and why should the user expect it?  .filetool.lst is a 'list of files to be backed up'  Such lists of files or variables containing files are quite commonly done with full paths. e.g. $PATH, $EDITOR, or even the lists acted on by command line tools to "do X to each file in list Y")

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: backup/restore error
« Reply #4 on: July 25, 2009, 11:25:15 PM »
If you are a new user there is  GUI tool which lets you select any file and it will be added to the .filetool.lst sans inital slash (Tools->Add to Filetool). Can't get easier than that.

If you are editing the file directly, one would think that one would notice all the other items are sans initial slash. Consistency matters.

It is a tar command warning to use relative paths. I shouldn't think that a non-turnkey system should need to pre-process such a simple file.

The tar -T option does not allow comments in such specified file. It is the requirement of the tar command and not specific to Tiny Core.

Editing any system file takes care and caution. If throwing consistency to the wind then one should not expect correct results.
« Last Edit: July 25, 2009, 11:38:58 PM by roberts »
10+ Years Contributing to Linux Open Source Projects.