Ubuntu Chroot ext3fs Partition

[Stephen Dedalus]

Hi all,

some weeks ago I installed Ubuntu Chroot on a new ext3fs Partition. Problem is now that I uninstalled it again, I think I lost some of my "hd" space, as there is only 4,2 GB left free. And i have nearly no extra apps installed, except a running and a mapping app.

Problem is i cant find the partition that i have created.

Is used this help to get ubuntu installed.

Ubuntu ChRoot + LXDE on Palm Pre. - xda-developers

I deleted the image. I reinstalled the phone with webos doctor. still only 4,2 gb of 8 gb available.

would be great i anyone of you could help me.

Regards
Ulrich

[MudShark22]

Have you tried tailor (get thru WOSQI or Preware) to reclaim the space?

[Stephen Dedalus]

Hi,

thank you for your help! I tried tailor befor but installed it again.

is says:

select partition:
there is just: usb(media) 6.078 GB
unused space: none

partition size: 6224
fs size: 6222
fs used: 2201
fs free: 4021

I checked filesystem and tried to enter new size, but of course I cant go over 6224.

regards
ulrich

[MudShark22]

it doesn't show the chroot ext3fs? Hmmm

[Stephen Dedalus]

Maybe i'm totally wrong. I just thought that 4.2 gb of free memory on a 8gb device. i can't remember that there was that less free memory left in the past.

this is what i get with lvdislay in terminal:

--- Logical volume ---
LV Name /dev/store/root
VG Name store
LV UUID dyc2SE-gy3x-TlRI-BP5V-cGv9-t9Oa-WL0NtE
LV Write Access read/write
LV Status available
# open 1
LV Size 456.00 MB
Current LE 57
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:0

--- Logical volume ---
LV Name /dev/store/var
VG Name store
LV UUID J3JXJ8-VG0Y-o9AA-y86G-9Joa-cl3b-3zjQZF
LV Write Access read/write
LV Status available
# open 1
LV Size 64.00 MB
Current LE 8
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1

--- Logical volume ---
LV Name /dev/store/update
VG Name store
LV UUID A0zd8W-73we-jhe6-PJPE-NZBg-TYpF-8p3lzz
LV Write Access read/write
LV Status available
# open 0
LV Size 16.00 MB
Current LE 2
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:2

--- Logical volume ---
LV Name /dev/store/log
VG Name store
LV UUID ALkc7D-hvOc-maqe-U1XX-nFDh-Nxfc-uGqgae
LV Write Access read/write
LV Status available
# open 1
LV Size 24.00 MB
Current LE 3
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:3

--- Logical volume ---
LV Name /dev/store/mojodb
VG Name store
LV UUID S0EUSr-sTGt-XuNk-y3NB-cF9K-rd55-DstH6U
LV Write Access read/write
LV Status available
# open 1
LV Size 144.00 MB
Current LE 18
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:4

--- Logical volume ---
LV Name /dev/store/filecache
VG Name store
LV UUID 6QhnvL-Q3mI-BmBh-Euck-wF2k-w0yp-auyDyH
LV Write Access read/write
LV Status available
# open 1
LV Size 136.00 MB
Current LE 17
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:5

--- Logical volume ---
LV Name /dev/store/swap
VG Name store
LV UUID WZwrj3-q4Fq-9RNy-ctj4-bu1I-o30N-nKOOlY
LV Write Access read/write
LV Status available
# open 1
LV Size 104.00 MB
Current LE 13
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:6

--- Logical volume ---
LV Name /dev/store/media
VG Name store
LV UUID 2q8EUx-tro2-ph6N-lUBU-ijoT-izCE-rTbEV2
LV Write Access read/write
LV Status available
# open 1
LV Size 6.08 GB
Current LE 778
Segments 3
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:7


Regards
Ulrich

[Stephen Dedalus]

Now I also did vgdisplay and pvdisplay. Does anyone see why I only can use 4 GB of the 8GB?

Thank you all.

vgdisplay
--- Volume group ---
VG Name store
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 82
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 8
Open LV 7
Max PV 0
Cur PV 1
Act PV 1
VG Size 7.00 GB
PE Size 8.00 MB
Total PE 896
Alloc PE / Size 896 / 7.00 GB
Free PE / Size 0 / 0
VG UUID 1I4sNv-4fvS-iQNY-iMjq-4PGf-h1Sd-yaYMCk

pvdisplay
--- Physical volume ---
PV Name /dev/mmcblk0p15
VG Name store
PV Size 7.02 GB / not usable 24.00 MB
Allocatable yes (but full)
PE Size (KByte) 8192
Total PE 896
Free PE 0
Allocated PE 896
PV UUID CfGiux-6oE9-5qjh-HbwB-Ygq2-AZ1v-ZIOxne

[geekpeter]

the link you provided that you said you followed does NOT create any partitions at all, it creates nothing more than an image file to use in place of a real partition, you should have got back all the space used the second you deleted the .img file.

i cant remember what name they ended up with but sometimes when i used .img files using that method after a bad crash id sometimes end up with a copy of the .img which was hidden (weird name with a . before the name), maybe use internalZ, have it show hidden files and have a good rummage around wherever you put the .img file, that guide makes it look like /media/internal, when i did it mine were in /media/cryptofs, so could be anywhere.

you will never reclaim ALL 8gb anyways, even with a freshly formatted 8gb usb stick you dont get to use all of it, even empty theres a fair bit missing, then theres webOS itsself which will use a fair chunk of it as well (same as with android and every other OS out there), then add in whatever media files you added, pics/music/etc.

[Stephen Dedalus]

Hi and thanks for your help,

in fact there was a copy of the image still on the flash. I used

find / -type f -size +20000k -exec ls -lh {} \; | awk '{ print $9 ": " $5 }'

to find all files over 20 MB size and there it was!!

Thanks alot for your help!

Problem solved

Regards
Ulrich