I am trying to create symbolic links of /data/sdext2/app/\* on /data/app. This is what I did in adb shell ln -sf /data/sdext2/app/\* /data/app/ But it is telling *"link failed No such file or directory"*. Note that none of the partitions are of FAT32 format. And without -f option it says *"link failed File exists"*.

As the subject indicates, does Android support any of the Extended File Systems ("ext", "ext2", "ext3" and "ext4") for removable storage cards (such as Micro SDXC storage cards)? Android is a Linux-based operating system, so surely such filesystems would be supported? My question relates to both Android 4.4-4.4.4 ("KitKat") and Android 5.0-5.1.1 ("Lollipop"), as I am just about to buy the Sony Xperia Z Ultra which runs the former, but has an upgrade available for "Lollipop"... The reason I ask is because Extended File Systems have a number of distinct advantages over Microsoft filesystems, and I do not use Microsoft Windows-based operating systems at all (well, at work I do - but personal stuff can't be used with their computers...), so it's only logical to utilize Extended Filesystems where possible, for the technical advantages.

[tag:link2sd] allows one to fully move apps to a second partition on the external sd card provided its Filesystem supports Linux permissions. but does it have to be a second partition or could I simply format the entire card e.g. ext3?would this still work when USB connecting to my PC?

Successfully installed CM7 on ZTE Blade and simple2ext (S2E ) made me excited. I've partitioned my SD in CWM recovery and I guess it was Ext3 partition. But one thing was mistake. I have checked in S2E checkbox says mount sd-ext partition as Ext4 and everything was okay until I wanted to make backup from recovery. All part passed succesfully but /sd-ext and I've googled this thread says : > "clockworkmod doesn't support ext4 on the blade. ext3 works." Unticking that checkbox makes all unworkable. What can I do now to make ext-partition to ext3 back and backup it succesfully by recovery? At this moment I want to make wipe or hard or factory reset to check something with clean android installation and then go back to my phone's current state. Maybe it's no need to make partition from ext4 to be ext3? ROM: CyanogenMod-7.2.0-RC1-blade-KANG (2.3.7 by BurgerZ) Kernel: 2.6.35.7-perf+

Does anyone know how I can enable ext2 or ext3 partitions on my LG Optimus V? I have already partitioned my 16GB SD card to 14.5 GB FAT32 and 500MB ext2. When using Link2SD it gives me a mount error. I am rooted but have not flashed any ROMs yet.

I have an external HDD with two partitions. Both are *ext3* partitions and works fine with Linux. When I plug the USB HDD in my Android device, it does not work. I see some errors in dmesg: [ 3132.712025] sd 206:0:0:0: [sda] Unhandled error code Following is the full log (also available at [Pastebin](http://pastebin.com/1yJ8iuBj)) :

[ 3129.797281] usb 1-1: new high-speed USB device number 84 using ehci-platform
[ 3129.948997] usb 1-1: New USB device found, idVendor=04fc, idProduct=0c25
[ 3129.949076] usb 1-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 3129.949118] usb 1-1: Product: USB to Serial-ATA bridge
[ 3129.949159] usb 1-1: Manufacturer: Sunplus Technology Inc.
[ 3129.949195] usb 1-1: SerialNumber: ST3500820A            9QMB89AR
[ 3129.956216] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 3129.956759] scsi206 : usb-storage 1-1:1.0
[ 3130.943497] scsi 206:0:0:0: Direct-Access     ST350082 0AS                   PQ: 0 ANSI: 2
[ 3130.947482] sd 206:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
[ 3130.948602] sd 206:0:0:0: Attached scsi generic sg0 type 0
[ 3130.950308] sd 206:0:0:0: [sda] Write Protect is off
[ 3130.950387] sd 206:0:0:0: [sda] Mode Sense: 38 00 00 00
[ 3130.953130] sd 206:0:0:0: [sda] No Caching mode page found
[ 3130.953203] sd 206:0:0:0: [sda] Assuming drive cache: write through
[ 3130.961231] sd 206:0:0:0: [sda] No Caching mode page found
[ 3130.961312] sd 206:0:0:0: [sda] Assuming drive cache: write through
[ 3131.096185] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3131.381492] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3131.676711] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3131.971902] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3132.267086] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3132.562270] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3132.712025] sd 206:0:0:0: [sda] Unhandled error code
[ 3132.712106] sd 206:0:0:0: [sda]  
[ 3132.712140] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[ 3132.712178] sd 206:0:0:0: [sda] CDB: 
[ 3132.712205] Read(10): 28 00 00 00 00 00 00 00 08 00
[ 3132.712305] end_request: I/O error, dev sda, sector 0
[ 3132.712345] Buffer I/O error on device sda, logical block 0
[ 3132.847682] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3133.142899] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3133.438095] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3133.733289] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3134.028505] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3134.323707] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3134.473244] sd 206:0:0:0: [sda] Unhandled error code
[ 3134.473324] sd 206:0:0:0: [sda]  
[ 3134.473357] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[ 3134.473396] sd 206:0:0:0: [sda] CDB: 
[ 3134.473422] Read(10): 28 00 00 00 00 00 00 00 08 00
[ 3134.473518] end_request: I/O error, dev sda, sector 0
[ 3134.473558] Buffer I/O error on device sda, logical block 0
[ 3134.609000] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3134.904220] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3135.199424] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3135.494638] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3135.789882] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3136.085081] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3136.234861] sd 206:0:0:0: [sda] Unhandled error code
[ 3136.234942] sd 206:0:0:0: [sda]  
[ 3136.234974] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[ 3136.235014] sd 206:0:0:0: [sda] CDB: 
[ 3136.235040] Read(10): 28 00 00 00 00 00 00 00 08 00
[ 3136.235136] end_request: I/O error, dev sda, sector 0
[ 3136.235177] Buffer I/O error on device sda, logical block 0
[ 3136.235299]  sda: unable to read partition table
[ 3136.244113] sd 206:0:0:0: [sda] No Caching mode page found
[ 3136.244198] sd 206:0:0:0: [sda] Assuming drive cache: write through
[ 3136.244248] sd 206:0:0:0: [sda] Attached SCSI disk
[ 3136.429360] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3136.724578] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3137.019861] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3137.315036] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3137.610218] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3137.905427] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3138.055309] sd 206:0:0:0: [sda] Unhandled error code
[ 3138.055385] sd 206:0:0:0: [sda]  
[ 3138.055422] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[ 3138.055459] sd 206:0:0:0: [sda] CDB: 
[ 3138.055485] Read(10): 28 00 00 00 00 00 00 00 f0 00
[ 3138.055583] end_request: I/O error, dev sda, sector 0
[ 3138.055622] Buffer I/O error on device sda, logical block 0
[ 3138.055684] Buffer I/O error on device sda, logical block 1
[ 3138.055720] Buffer I/O error on device sda, logical block 2
[ 3138.055755] Buffer I/O error on device sda, logical block 3
[ 3138.055790] Buffer I/O error on device sda, logical block 4
[ 3138.055824] Buffer I/O error on device sda, logical block 5
[ 3138.055858] Buffer I/O error on device sda, logical block 6
[ 3138.180976] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3138.466284] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3138.751642] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3139.037079] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3139.332211] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3139.627405] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3139.777006] sd 206:0:0:0: [sda] Unhandled error code
[ 3139.777088] sd 206:0:0:0: [sda]  
[ 3139.777119] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[ 3139.777162] sd 206:0:0:0: [sda] CDB: 
[ 3139.777190] Read(10): 28 00 00 00 00 00 00 00 08 00
[ 3139.777288] end_request: I/O error, dev sda, sector 0
[ 3139.777323] quiet_error: 23 callbacks suppressed
[ 3139.777358] Buffer I/O error on device sda, logical block 0
[ 3139.962008] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3140.257168] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3140.552444] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3140.847589] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3141.142778] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3141.437970] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3141.587839] sd 206:0:0:0: [sda] Unhandled error code
[ 3141.587922] sd 206:0:0:0: [sda]  
[ 3141.587956] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[ 3141.587993] sd 206:0:0:0: [sda] CDB: 
[ 3141.588021] Read(10): 28 00 00 00 00 00 00 00 f0 00
[ 3141.588121] end_request: I/O error, dev sda, sector 0
[ 3141.588162] Buffer I/O error on device sda, logical block 0
[ 3141.588228] Buffer I/O error on device sda, logical block 1
[ 3141.588265] Buffer I/O error on device sda, logical block 2
[ 3141.588300] Buffer I/O error on device sda, logical block 3
[ 3141.588335] Buffer I/O error on device sda, logical block 4
[ 3141.588369] Buffer I/O error on device sda, logical block 5
[ 3141.588405] Buffer I/O error on device sda, logical block 6
[ 3141.588441] Buffer I/O error on device sda, logical block 7
[ 3141.588477] Buffer I/O error on device sda, logical block 8
[ 3141.723340] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3142.008700] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3142.294008] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3142.579457] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3142.874631] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3143.169809] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3143.319518] sd 206:0:0:0: [sda] Unhandled error code
[ 3143.319599] sd 206:0:0:0: [sda]  
[ 3143.319633] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[ 3143.319672] sd 206:0:0:0: [sda] CDB: 
[ 3143.319700] Read(10): 28 00 00 00 00 00 00 00 08 00
[ 3143.319798] end_request: I/O error, dev sda, sector 0
[ 3143.484670] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3143.799687] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3144.094726] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3144.389973] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3144.685229] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3144.980369] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3145.129772] sd 206:0:0:0: [sda] Unhandled error code
[ 3145.129809] sd 206:0:0:0: [sda]  
[ 3145.129823] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[ 3145.129840] sd 206:0:0:0: [sda] CDB: 
[ 3145.129853] Read(10): 28 00 00 00 00 00 00 00 f0 00
[ 3145.129896] end_request: I/O error, dev sda, sector 0
[ 3145.255897] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3145.541259] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3145.826603] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3146.112009] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3146.407167] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3146.702336] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3146.852225] sd 206:0:0:0: [sda] Unhandled error code
[ 3146.852306] sd 206:0:0:0: [sda]  
[ 3146.852338] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[ 3146.852380] sd 206:0:0:0: [sda] CDB: 
[ 3146.852407] Read(10): 28 00 00 00 00 00 00 00 08 00
[ 3146.852503] end_request: I/O error, dev sda, sector 0
[ 3146.852538] quiet_error: 52 callbacks suppressed
[ 3146.852573] Buffer I/O error on device sda, logical block 0
[ 3147.046747] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3147.341944] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3147.637250] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3147.932432] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3148.227603] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3148.522749] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3148.672173] sd 206:0:0:0: [sda] Unhandled error code
[ 3148.672213] sd 206:0:0:0: [sda]  
[ 3148.672227] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[ 3148.672243] sd 206:0:0:0: [sda] CDB: 
[ 3148.672255] Read(10): 28 00 00 00 00 00 00 00 f0 00
[ 3148.672300] end_request: I/O error, dev sda, sector 0
[ 3148.672319] Buffer I/O error on device sda, logical block 0
[ 3148.672350] Buffer I/O error on device sda, logical block 1
[ 3148.672366] Buffer I/O error on device sda, logical block 2
[ 3148.672381] Buffer I/O error on device sda, logical block 3
[ 3148.672396] Buffer I/O error on device sda, logical block 4
[ 3148.672411] Buffer I/O error on device sda, logical block 5
[ 3148.672426] Buffer I/O error on device sda, logical block 6
[ 3148.672440] Buffer I/O error on device sda, logical block 7
[ 3148.672455] Buffer I/O error on device sda, logical block 8
[ 3148.798335] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3149.093531] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3149.388697] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3149.683817] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3149.979098] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3150.274320] usb 1-1: reset high-speed USB device number 84 using ehci-platform
[ 3150.423545] sd 206:0:0:0: [sda] Unhandled error code
[ 3150.423576] sd 206:0:0:0: [sda]  
[ 3150.423586] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[ 3150.423597] sd 206:0:0:0: [sda] CDB: 
[ 3150.423607] Read(10): 28 00 00 00 00 00 00 00 08 00
[ 3150.423636] end_request: I/O error, dev sda, sector 0

I see the device at /dev/block/sda but I don't have any idea about mounting it manually. I was expecting /dev/block/sda1 and /dev/block/sda2. How do I manage those partitions?

I have installed the [Link2SD](https://play.google.com/store/apps/details?id=com.buak.Link2SD) application on my Samsung Galaxy Ace, everything is in place, now I dont understand how it works. I have allotted 1GB of space to my second ext3 partition, I have 2 doubts: 1. Whenever I link my application, those space does not gets deducted from internal memory, I checked in *Settings → Manage Application* 2. When I move the application to SD card, still I have some space occupied in internal memory I don't understand the exact use of Link2SD: if I allotted 1GB of space for the apps, then why my internal space is being used -- and if Link2SD does work like this only, then I would better use force move application using adb shell, which even does not require rooting. Can anyone please clarify my doubts, and let me know how can I use *Link2SD*, so that everything is moved to SD Card and nothing remains in internal memory?

Recently I happened to switch back to stock ROM in my LG P500. I used v2.3.3 (v20c) ROM from LG's site and installed wiping all partitions including my SD card. I then rooted using SuperOneClick and installed Link2SD. I rebooted into TWRP recovery, partitioned my SD card with one ext3 and one swap partition. The remaining space on the SD card was filled with a FAT partition. After rebooting phone normally, I used Link2SD which detected the presence of ext3 and **mounted it successfully at very first run**. To test the mount, I restated the phone (with reboot command in terminal emulator) and the ext3 partition was mounted without any problems. Having faced a issue with ext3 partitions (see my earlier question ) I decided to first test the backup and restore features first. Hence I moved Google Maps app to ext partition and created a link. With link created, maps was working fine. I then took a backup with TWRP which included all partitions (system, data, boot, recovery, cache, .android_secure and sd-ext). I immediately restored the backup and to my surprise, Link2SD did not mount the partition and reported an error invalid argument. My phone does not have busybox installed and also no init.d support. But even without these Link2SD mounted the second partition well and fails after restore. Can someone explain why it fails to mount after restore when it did before? **Update**: I had sent email to the developer of Link2SD with logcat and as of now I haven't got any reply. The log cat did not show any suspicious entries (or I do not know what to look for!). The only two lines about Link2SD are: > I/ActivityManager( 1567): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.buak.Link2SD/.Link2SD } from pid 1680 I/ActivityManager( 1567): com.android.server.am.ActivityRecord 444 Displayed com.buak.Link2SD/.Link2SD: +387ms This logcat is also available here for a detailed view. **Update 2**: I missed to add that, with Link2Sd not mounting, if I go ahead and format the SD card and re-partition using TWRP recovery, Link2SD starts recognizing and mounting. So, something happens to the partition during restore operation. At next available opportunity, I will attempt to manually mount the partition as Izzy had kindly suggested.

I've read a bit here on Android Enthusiasts and I've been able to partition my sdcard. A partition FAT32 and another one ext3, using the AmonRa Recovery for Acer Liquid Metal. Everything looks fine and if I start titanium backup I see on overview screen: > Internal: 193 mb (60.2 mb free). SD card: 6.87 GB (520 mb free). SD card (a2sd): 958 MB (958 MB free) So it looks like I'm not using that partition, right? I've tried moving application with app2sd pro and titanium backup to sd card but the ext3 partition does not get filled. What's wrong?

I have an Archos 101IT with a 16G external SD card. The SD card contains one partition that is formatted as an ext3 file system. The Archos runs UrukDroid 1.6.4 (Froyo 2.2). The Problem: When booted, the SD card is mounted with the following mount options: /dev/block/vold/179:17 on /mnt/storage/sdcard type ext3 (rw,nosuid,nodev,noexec,noatime,nodiratime,fmode=0666,dmode=0666,errors=continue,data=ordered) The fmode and dmode options make it impossible to use file permissions, in particular it is not possible to make files read-only. This is needed by the Titanium Backup tool to protect backups from being overwritten. I can change the mount options with a remount: # mount /mnt/storage/sdcard -o remount,fmode=0,dmode=0 The Question: How can I have the SD card mounted with the right mount options upon boot?

I partitioned my MicroSD card and created 1GB ext3 partition. - What is the next step so I can use it to make the performance of my android better? It seems to me that it is mounted into /sd-ext - What are all the options I can use ext for? ------- CM7 on HTC Desire

I'm trying to partition my SD card with a ~31gb FAT32 partition and a 1024mb ext3 partition for A2SD. I've tried making the partitions with CMW-Alpharev Recovery v2.5.1.8 and with gParted (on a bootable live USB stick) and neither works. Basically, whenever I try to create a second partition on the card, the second (or later) partition doesn't work anywhere. It's not recognized by my phone, Windows or gParted (even right after parttitioning). The first partition does work, though. So if the ext3 is first, the FAT32 doesn't work and vice versa. I have no clue as to what could be causing this or how to fix it, any suggestions?

I'm trying to make Link2SD work on my phone so I partitioned my 16gb SD to 4gb for the Ext3 partition and the rest for normal storage. I'm noticing some slight lag on my usage of the phone and I read on this article that I can in fact, increase the read cache to speed up reading contents on the SD. My question is; does increasing the read cache also affect the speed of reading my Ext3 partition? Or does it only affect the "normal" storage?