microSD && ext3 file system

Matthias Apitz guru at unixarea.de
Wed Apr 4 19:48:49 CEST 2012


El día Tuesday, April 03, 2012 a las 07:06:40PM +0200, Ed Kapitein escribió:

> Hi Matthias,
> 
> A while ago i read this article on [1].
> Perhaps this will help you to solve your problem.
> ( i have a hard time finding a working uSD card too )
> Is your card on the supported card list [2] ?
> 
> Kind regards,
> Ed
> 
> [1] https://lwn.net/Articles/428584/
> [2] http://wiki.openmoko.org/wiki/Supported_microSD_cards

Hi,

This card (or the reader in the FR) must be completely broken; the FR
was one day switched off and now a ls(1) in a directory where should only
be subdirs (as numbers for OpenStreetMap) looks like this:

root at om-gta02 /media/card/osm # ls -l
-r-xr-xr-x    1 root     root            0 Sep 29  2034 06.4.25
.sam
drwxr-xr-x    6 root     root         4096 Apr  3  2012 15
drwxr-xr-x    5 root     root         4096 Apr  3  2012 16
drwxr-xr-x    6 root     root         4096 Apr  3  2012 17
drwxr-xr-x   48 root     root         4096 Oct 12  2009 8
drwxr-xr-x   51 root     root         4096 Jun 16  2009 9
-r-xr-xr-x    1 root     root    1936026729 Mar  9  2030 =2.4.2
w.ord
-rwxr-xr-x    1 root     root    808598885 Jan 10  2030 iption=m.ade
-rwxr-xr-x    1 root     root    1852795251 Dec  5  1902 stardict.'s
-rwxr-xr-x    1 root     root           74 Apr  2  2012 syncToMoko.sh

I also do not understand why df(1) shows the space a ~1GB and the
fdisk(1M) as 3.8GB:

root at om-gta02 /media/card/osm # df -kh /media/card
Filesystem                Size      Used Available Use% Mounted on
/dev/mmcblk0p1         1022.0M    552.5M    469.4M  54% /media/card
root at om-gta02 /media/card/osm # fdisk -l /dev/mmcblk0

Disk /dev/mmcblk0: 3953 MB, 3953131520 bytes
4 heads, 16 sectors/track, 120640 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Disk identifier: 0x0aecb0ac

        Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk0p1               1      120640     3860472   83  Linux

And even more surprises: after reading the OSM tiles with tangoGPS, the
dir changes now to:

root at om-gta02 /media/card/osm # ls -l
-r-xr-xr-x    1 root     root            0 Sep 29  2034 06.4.25
.sam
drwxr-xr-x    4 root     root         4096 Jan  2 06:56 10
drwxr-xr-x    5 root     root         4096 Jan  2 06:56 11
drwxr-xr-x    5 root     root         4096 Jan  2 06:56 12
drwxr-xr-x    5 root     root         4096 Jan  2 06:55 13
drwxr-xr-x    5 root     root         4096 Jan  2 06:54 14
drwxr-xr-x    6 root     root         4096 Apr  3  2012 15
drwxr-xr-x    5 root     root         4096 Apr  3  2012 16
drwxr-xr-x    6 root     root         4096 Apr  3  2012 17
drwxr-xr-x    5 root     root         4096 Jan  2 06:57 7
drwxr-xr-x   48 root     root         4096 Oct 12  2009 8
drwxr-xr-x   51 root     root         4096 Jun 16  2009 9
-r-xr-xr-x    1 root     root    1936026729 Mar  9  2030 =2.4.2
w.ord
-rwxr-xr-x    1 root     root    808598885 Jan 10  2030 iption=m.ade
-rwxr-xr-x    1 root     root    1852795251 Dec  5  1902 stardict.'s
-rwxr-xr-x    1 root     root           74 Apr  2  2012 syncToMoko.sh

What does all this mean?

What should I do?

	matthias

-- 
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e <guru at unixarea.de> - w http://www.unixarea.de/
UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5



More information about the community mailing list