Active Topics
-
Which is the best N95? What software modifications could be made to it? (3)
to General by Kalatti - 3 hrs, 12 mins ago -
Installing CSSU Stable in year 2024 (2)
to Maemo 5 / Fremantle by teroyk - 10 hrs, 40 mins ago -
Porting apps to Leste (34)
to Maemo 7 / Leste by Arno_11 - 20 hrs, 16 mins ago -
[ANNOUNCE] CSSU-thumb thread - stable Thumb2 on N900 (2,266)
to Maemo 5 / Fremantle by pali - 2 days, 12 hrs ago -
Firefox with Leste (7)
to Maemo 7 / Leste by teroyk - 2 days, 16 hrs ago - more...
|
2010-09-14
, 21:13
|
|
Posts: 2,829 |
Thanked: 1,459 times |
Joined on Dec 2009
@ Finland
|
#2
|
What filesystem on mmc1? How big file?
 |
|
2010-09-14
, 21:45
|
|
Posts: 168 |
Thanked: 58 times |
Joined on Aug 2010
@ Vienna
|
#3
|
Originally Posted by slender
/media/mmc1 is mounted as vfat.
What filesystem on mmc1? How big file?
But the error also occurs when doing it on /home which is ext3.
file is ~ 232MB which should be no problem for vfat or ext3
Internet only says:
http://www.mail-archive.com/busybox@.../msg04880.html
tar -v says "BusyBox v1.10.2"
:-(
|
|
2010-09-14
, 21:58
|
|
Posts: 2,802 |
Thanked: 4,491 times |
Joined on Nov 2007
|
#4
|
Originally Posted by ME2g
The output of tar just before the error message should be a big hint ;-)
When I am using tar to pack files with
tar -cvzf /media/mmc1/backup.tar.gz /
What can I do?
| The Following User Says Thank You to lma For This Useful Post: | ||
 |
|
2010-09-15
, 05:55
|
|
Posts: 466 |
Thanked: 180 times |
Joined on Feb 2010
|
#5
|
You need to exclude /sys & /proc at the very least. You probably also want to exclude other filesystems like /media/mmc1 and python bind mounts.
Try this
Code:
sudo gainroot mount --bind / /mnt tar -cvzf /media/mmc1/backup.tar.gz /mnt
Last edited by clasificado; 2010-09-15 at 05:58.
| The Following User Says Thank You to clasificado For This Useful Post: | ||
| The Following User Says Thank You to lma For This Useful Post: | ||
|
|
2010-09-15
, 19:28
|
|
Posts: 992 |
Thanked: 995 times |
Joined on Dec 2009
@ California
|
#7
|
Is it joke?
I mean - recursive write of tar file. Commands like "tar cvf somefile /" will never ends until the space on somefile file system is exhausted. Because tar will try to write somefile into somefile!
If you want to make a copy of root file system you should use a full tar (install it from repository) and use a parameter "-l" (or "--one-file-system"). By default tar will go through mount points and write all stuff from it including "somefile" content too.
I mean - recursive write of tar file. Commands like "tar cvf somefile /" will never ends until the space on somefile file system is exhausted. Because tar will try to write somefile into somefile!
If you want to make a copy of root file system you should use a full tar (install it from repository) and use a parameter "-l" (or "--one-file-system"). By default tar will go through mount points and write all stuff from it including "somefile" content too.
 |
|
2010-09-15
, 19:33
|
|
Posts: 2,473 |
Thanked: 12,265 times |
Joined on Oct 2009
@ Jerusalem, PS/IL
|
#8
|
BusyBox is one f'd up tool, install tar-gnu and use gtar instead.
|
|
2010-09-15
, 20:54
|
|
Posts: 2,802 |
Thanked: 4,491 times |
Joined on Nov 2007
|
#9
|
Originally Posted by egoshin
Nah, it's smart enough to figure that particular trap out by itself and skip the tarball it's in the process of writing.
I mean - recursive write of tar file. Commands like "tar cvf somefile /" will never ends until the space on somefile file system is exhausted. Because tar will try to write somefile into somefile!
Originally Posted by MohammadAG
GNU tar will also get into helical underwear syndrome if you try to archive /sys, just in a different way. A lot of the files in there lie about their size and you're not meant to tar them up anyway, so just don't.
BusyBox is one f'd up tool, install tar-gnu and use gtar instead.
|
|
2010-09-15
, 23:09
|
|
Posts: 992 |
Thanked: 995 times |
Joined on Dec 2009
@ California
|
#10
|
Originally Posted by lma
It doesn't work sometime, especially on mounted FS etc.
Nah, it's smart enough to figure that particular trap out by itself and skip the tarball it's in the process of writing
When I am using tar to pack files with
tar -cvzf /media/mmc1/backup.tar.gz /
or
tar -cvf /media/mmc1/backup.tar /
onto the SD card as root user I am getting
"tar: short read"
and the tar file is garbage.
:-(
What can I do?
(I am used to Linux so if there is an alternative I can try please tell me, but normally tar should work on a Linux system!)