Active Topics
-
[ANNOUNCE] MeeShop - new app store (8)
to Applications by Maemish - 4 hrs, 1 min ago -
HTTP-401 Sfos-Builder when using /etc/ssu credentials (0)
to SailfishOS by insanelysexy - 8 hrs, 30 mins ago -
Longtime users: What device(s) are you using today? (54)
to General by ryu1 - 2 days, 13 hrs ago -
Registering (1)
to General by Halftux - 5 days, 6 hrs ago -
Applications Wishlist (55)
to Maemo 7 / Leste by sixwheeledbeast - 6 days, 8 hrs ago - more...
egnat69 |
2014-01-20
, 09:57
|
|
Posts: 54 |
Thanked: 22 times |
Joined on Jan 2014
|
#11
|
Originally Posted by Leinad
no expert on this topic but not entirely sure about performance issues due to the speed of that sd-port in general... would be really happy if you could look into this a bit during testing your solutions ;D
|
|
2014-01-20
, 19:30
|
|
Posts: 594 |
Thanked: 1,094 times |
Joined on Aug 2012
@ Rhine
|
#12
|
Originally Posted by egnat69
yes, i had the same thought, but could not notice any difference in speed the last day, using it.
no expert on this topic but not entirely sure about performance issues due to the speed of that sd-port in general... would be really happy if you could look into this a bit during testing your solutions ;D
This is, what df -h now puts out with my configuration:
Code:
[nemo@localhost ~]$ df -h Filesystem Size Used Avail Use% Mounted on rootfs 14G 4.1G 9.2G 31% / /dev/mmcblk0p28 14G 4.1G 9.2G 31% / devtmpfs 406M 64K 406M 1% /dev tmpfs 407M 268K 406M 1% /dev/shm tmpfs 407M 23M 384M 6% /run tmpfs 407M 0 407M 0% /sys/fs/cgroup tmpfs 407M 24K 407M 1% /tmp /dev/mmcblk0p25 8.0M 4.2M 3.8M 54% /persist /dev/mmcblk0p19 8.0M 4.1M 3.9M 52% /drm /dev/mmcblk0p18 64M 45M 20M 70% /firmware /dev/mmcblk0p28 14G 4.1G 9.2G 31% /swap /dev/mmcblk0p28 14G 4.1G 9.2G 31% /home /dev/mmcblk0p9 48M 7.5M 40M 16% /var/systemlog /dev/mmcblk1p1 60G 2.6G 54G 5% /mnt/sdcard2 /dev/mmcblk1p1 60G 2.6G 54G 5% /home/nemo /dev/mmcblk1p1 60G 2.6G 54G 5% /data/sdcard tmpfs 407M 0 407M 0% /mnt/asec tmpfs 407M 0 407M 0% /mnt/obb /dev/mmcblk1p1 60G 2.6G 54G 5% /run/user/100000/media/sdcard /dev/mmcblk1p1 60G 2.6G 54G 5% /home/nemo /dev/mmcblk1p1 60G 2.6G 54G 5% /data/sdcard
edit: i don't understand, why /home/nemo and /data/sdcard are listed 2 times for example...
Last edited by Leinad; 2014-01-20 at 19:53.
|
|
2014-01-21
, 13:37
|
|
Posts: 594 |
Thanked: 1,094 times |
Joined on Aug 2012
@ Rhine
|
#13
|
There was at least one little problem with my config:
all media (pictures, videos, documents, ...) was shown twice.
my assuption was, it's because it's found in
/home/nemo and in /mnt/sdcard2/home
so i renamed /mnt/sdcard2/home to /mnt/sdcard2/.home and adapted the script.
now everything seems to work fine again. will update first post.
all media (pictures, videos, documents, ...) was shown twice.
my assuption was, it's because it's found in
/home/nemo and in /mnt/sdcard2/home
so i renamed /mnt/sdcard2/home to /mnt/sdcard2/.home and adapted the script.
now everything seems to work fine again. will update first post.
 |
|
2014-01-21
, 20:15
|
|
Posts: 2,355 |
Thanked: 5,249 times |
Joined on Jan 2009
@ Barcelona
|
#14
|
Originally Posted by Leinad
Errrrrr.... WHY?
it uses tmpfs and is limited to ~400MB on Jolla and will be gone after every reboot, so IMHO absolutely not usefull for mounting the sdcard.
The limits you describe are correct... for the tmpfs mount itself! They will not apply to whatever you store inside the sdcard mountpoint.
If you let the default mountpoint, then your changes simplify quite a lot: you just need to bind mount the Android sdcard directory, and that's about it.
|
|
2014-01-22
, 07:33
|
|
Posts: 594 |
Thanked: 1,094 times |
Joined on Aug 2012
@ Rhine
|
#15
|
Originally Posted by javispedro
Well, there are 2 main reasons
Errrrrr.... WHY?
- i want to be able to store more than 400M on my 64G card
- i want the stored data to be still there after a reboot
Originally Posted by javispedro
by default, there is no other mountpoint than the tmpfs-mountpoint. When i bind mount folders to the default tmpfs mountpoint, they have the same limitations!
The limits you describe are correct... for the tmpfs mount itself! They will not apply to whatever you store inside the sdcard mountpoint.
If you let the default mountpoint, then your changes simplify quite a lot: you just need to bind mount the Android sdcard directory, and that's about it.
Just to show you, what i mean, i mounted it the way you suggested and here's the output:
Code:
[root@localhost nemo]# mount -o bind /run/user/100000/media/sdcard /home/nemo [root@localhost nemo]# mount -o bind /run/user/100000/media/sdcard /data/sdcard
Code:
[root@localhost nemo]# df -h Filesystem Size Used Avail Use% Mounted on rootfs 14G 4.1G 9.2G 31% / /dev/mmcblk0p28 14G 4.1G 9.2G 31% / devtmpfs 406M 64K 406M 1% /dev tmpfs 407M 72K 407M 1% /dev/shm tmpfs 407M 33M 374M 9% /run tmpfs 407M 0 407M 0% /sys/fs/cgroup tmpfs 407M 8.0K 407M 1% /tmp /dev/mmcblk0p25 8.0M 4.2M 3.8M 54% /persist /dev/mmcblk0p19 8.0M 4.1M 3.9M 52% /drm /dev/mmcblk0p9 48M 7.1M 41M 15% /var/systemlog /dev/mmcblk0p18 64M 45M 20M 70% /firmware /dev/mmcblk0p28 14G 4.1G 9.2G 31% /swap /dev/mmcblk0p28 14G 4.1G 9.2G 31% /home tmpfs 407M 0 407M 0% /mnt/asec tmpfs 407M 0 407M 0% /mnt/obb tmpfs 407M 33M 374M 9% /home/nemo tmpfs 407M 33M 374M 9% /data/sdcard
|
|
2014-01-22
, 07:54
|
|
Posts: 2,355 |
Thanked: 5,249 times |
Joined on Jan 2009
@ Barcelona
|
#16
|
Obviously, you need to mount the sd card ...
Also, you must mount the sdcard before creating the bind mount. Mounts don't propagate over to bind mounts by default. Alternatively, you might use --make-shared to ensure they are propagated, but this option is poorly documented.
Also, you must mount the sdcard before creating the bind mount. Mounts don't propagate over to bind mounts by default. Alternatively, you might use --make-shared to ensure they are propagated, but this option is poorly documented.
| The Following User Says Thank You to javispedro For This Useful Post: | ||
|
|
2014-01-22
, 08:17
|
|
Posts: 594 |
Thanked: 1,094 times |
Joined on Aug 2012
@ Rhine
|
#17
|
Sorry, i'm afraid, i don't understand, what you mean...
What exactly would you do different? Could you please provide some lines of Code to show, what you mean?
As i said, i'm no expert and happy for every improvement!
Originally Posted by javispedro
that's what i do with
Obviously, you need to mount the sd card ...
Code:
mount /dev/mmcblk1p1 /mnt/sdcard2
Originally Posted by javispedro
i do...
Also, you must mount the sdcard before creating the bind mount.
What exactly would you do different? Could you please provide some lines of Code to show, what you mean?
As i said, i'm no expert and happy for every improvement!
|
|
2014-01-22
, 09:30
|
|
Posts: 2,355 |
Thanked: 5,249 times |
Joined on Jan 2009
@ Barcelona
|
#18
|
In the df output you attached there is no sd card mounted.
An example:
If you undo your modifications, after reboot, your sdcard gets mounted to
/run/user/100000/media/sdcard .
Afterwards, just run:
Are there any problems with the above (except that it is not automated)?
To automate it all you have to do is to ensure it is done _after_ mounting the SD card. That means that either you edit the mount-sd.sh script or insert a new udev event handler.
An example:
If you undo your modifications, after reboot, your sdcard gets mounted to
/run/user/100000/media/sdcard .
Afterwards, just run:
Code:
mount -o bind /run/user/100000/media/sdcard /data/sdcard
To automate it all you have to do is to ensure it is done _after_ mounting the SD card. That means that either you edit the mount-sd.sh script or insert a new udev event handler.
| The Following User Says Thank You to javispedro For This Useful Post: | ||
|
|
2014-01-22
, 10:02
|
|
Posts: 594 |
Thanked: 1,094 times |
Joined on Aug 2012
@ Rhine
|
#19
|
i'm not sure, why the mount of the sdcard is missing in the output above, but it was mounted on /run/user/100000/media/sdcard
i undid all my modifications and ran
i tried the same some days ago and the output looked like
and that's exactly the main problem:
i was not able to store more than 400MB on the sdcard, because the limitations of /run/user/100000/media/sdcard go over to /data/sdcard if mounted that way!
Last edited by Leinad; 2014-01-24 at 11:15.
i undid all my modifications and ran
Code:
mount -o bind /run/user/100000/media/sdcard /data/sdcard
Code:
... tmpfs 407M 33M 374M 9% /run/user/100000/media/sdcard tmpfs 407M 33M 374M 9% /data/sdcard
i was not able to store more than 400MB on the sdcard, because the limitations of /run/user/100000/media/sdcard go over to /data/sdcard if mounted that way!
Last edited by Leinad; 2014-01-24 at 11:15.
|
|
2014-01-22
, 11:20
|
|
Posts: 131 |
Thanked: 241 times |
Joined on Feb 2012
|
#20
|
The problem is that /run/user/100000/media/sdcard is not mounted to the sdcard /dev/mmcblk1p1.
All subfolder of /run are tmpfs. This means that a mount -o bind /run/... /media/sdcard leads to that /media/sdcard points also to tmpfs.
Be sure that /run/user/100000/media/sdcard is mounted with
The SOURCE must be /dev/mmcblk1p1!
Then, mount -o /run/user/100000/media/sdcard /data/sdcard should work correctly.
On my Jolla i have access to 59G on /run/user/100000/media/sdcard and /data/sdcard/sdcard and both are pointing to /dev/mmcblk1p1.
Last edited by HolgerN; 2014-01-22 at 11:23.
All subfolder of /run are tmpfs. This means that a mount -o bind /run/... /media/sdcard leads to that /media/sdcard points also to tmpfs.
Be sure that /run/user/100000/media/sdcard is mounted with
findmnt /run/user/100000/media/sdcard
Then, mount -o /run/user/100000/media/sdcard /data/sdcard should work correctly.
On my Jolla i have access to 59G on /run/user/100000/media/sdcard and /data/sdcard/sdcard and both are pointing to /dev/mmcblk1p1.
Last edited by HolgerN; 2014-01-22 at 11:23.
| The Following User Says Thank You to HolgerN For This Useful Post: | ||