Given that /system and a few other partitions are ext4 already, I know kernel support is built it. I'm guessing I'd need to root the device and edit the script that mounts/unmounts the microSD card. Anyone else know an easier way to do it? Apparently noone who manufactures tablets needs files over 4GB...Idiots.
I may give this a try today to see if I can figure out an easy way to do it. Although, I really need TrueCrypt support since most of my external drives are truecrypt containers. :-(
I suppose with root access it'd be a simple matter of mount -t ext4 /dev/block/whateversdcards /mnt/sdcard
I've still yet to root my device to test it though.
Did you ever give this a try?
It would be even cooler if we could convert the internal sdcard to ext4. It seems to be FAT32 as well. Then we could do a symlink under sdcard to the micro.
Related
Hello
Sometimes i want to move file that's bigger then 4G to a sd-cart. Unfortunately FAT32 don't support this
So I asked google and google didn't know eather, but he gave me interesting project. Android-x86
Android-x86 supports NTFS as file system.
So i was wandering, if in kernel i turn module ntfs on, will i be possible to convert fat32 partition to ntfs?
will it work then?
[edit] I know I can change fat32 to ext3/4 but will it be mounted to /sd-cart/ so i'll be able to write/read it from the phone?[/edit]
really interesting any news about this???
anyway some notice about other platform??? how is it possible that still today don't exist an operative system for smartphone with filesystem support more than old fat32 4gb data??? this has no sense for me
confiq said:
[edit] I know I can change fat32 to ext3/4 but will it be mounted to /sd-cart/ so i'll be able to write/read it from the phone?[/edit]
Click to expand...
Click to collapse
I realise I'm replying to an old post but as there's been recent activity on this thread...
I'd just use an ext2 partition. If you're running A2SD you probably have one already. I run MCR 3.2 on my Hero & this partition is mounted (as a result of A2SD) on /system/sd & is obviously read/write. Max filesize under ext2/3 is 16GB for a 1KB blocksize.
anything happen with this? with the wealth of tablets coming out with the ability to mount host powered usb harddrives it would be great to be able to read/write (or even just read) ntfs natively within Android. formatting to Ext3 is the only option at the moment and is a bit of a ballache if i want to use the drive for anything else or take it to a friends etc.
thefunkygibbon said:
anything happen with this? with the wealth of tablets coming out with the ability to mount host powered usb harddrives it would be great to be able to read/write (or even just read) ntfs natively within Android. formatting to Ext3 is the only option at the moment and is a bit of a ballache if i want to use the drive for anything else or take it to a friends etc.
Click to expand...
Click to collapse
Havent heard anything yet. But you can use the EXT2/3 FS driver for windows to make your life a little easier. I use it when I pull hdds out of my NAS.
http://www.fs-driver.org/
Can I have external card mounted as ext2? I have files names not supported by fat and sync'ed with dropbox
Yes, you can but afaik there is no easy way to do this.
I formatted my sdcard to ext2 (because I wanted to put large file (image for wikipedia offline) on my sdcard).
I formatted the beginning (~30MB) of my sdcard to fat32 so that the Nook detect the sdcard and does not trigger an error and the remaining part to ext2.
Then I used a script that mount manually the ext2 partition to /sdcard on boot.
This generally works but I have sometimes a few bug in some applications, especially when I connect and disconnect my Nook to my computer...
The best solution would be to find a way so that Android can automount a ext2 partition by itself but I don't know how to do it.
Instead of using the whole card I partitioned the first 4gb as fat16 (msdos) and then set the rest to ext3. When the fat16 space runs out I'll look into making some sort of script to try to mount the second partition. At the moment with the card acts like a normal 4gb card.
is it possible to repartition the nook to be able to use the space that b&n reserves for its contents? I heard that the space for our files is just 250 mb.
user4242 said:
is it possible to repartition the nook to be able to use the space that b&n reserves for its contents? I heard that the space for our files is just 250 mb.
Click to expand...
Click to collapse
yes of course. If you're used to linux repartitioning and the dd command then it's a breeze. If you're a Windows user who've never done partitioning or disk imaging then you can easily mess up.
I'll assume the former.
It's just a case of:
boot with a noogie.img that you've written to a sdcard (root of card, not partition 1)
then plug it in
now you can see all the nook partitions like it's an external USB drive and fdisk, cfdisk, partitionmagic or whatever you want
Obviously you're gonna want to backup first because if you mess up the only way to restore would be asking one of us off this forum to break the distribution laws and send you a 2gb (or whatever it is) image.
All the details on this forum
Has someone tried editing /system/etc/vold.conf to get a ext-formated SD-Card mounted?
mali100 said:
Has someone tried editing /system/etc/vold.conf to get a ext-formated SD-Card mounted?
Click to expand...
Click to collapse
I checked, I had modified it adding a line "partition 2" in the section "volume_sdcard2" so that Android does not show the message "SD card blank or has unsupported filesystem".
But I couldn't make it mount a ext2 sdcard itself. (if you know how to do it without using another script, I'm interested)
Time to resurrect this thread.
FAT is ugly. File timestamps are in local time (whatever that means, summer? winter?).
The Nook vfat implementation has problems with caching in and out directory info on vfat
and intermittently changes all the modify timestamps by 1, 4 or 5 hours.
This can play havoc if you are trying to keep things synchronized by filetime.
I've decided to have my SD card be ext3
Our volume demon, /system/bin/vold (which is ancient) uses /system/etc/vold.conf to configure automounting.
It presumes that all volumes are vfat.
It seems from a brief look inside that it does handle ext2 and ext3 somehow.
There is also the question of getting it to automount USB drives.
The easiest solution to ext3 on the SD card is to make it non-removable.
First, delete the second section out of vold.conf that relates to the SD card.
Then edit init.rc:
Code:
mkdir /sdcard 0777 system system
...
mount ext3 /dev/block/mmcblk1p1 /sdcard nosuid nodev noatime nodiratime uid=1000,gid=1015,fmask=117,dmask=007
chown system sdcard_rw /sdcard
chmod 0770 /sdcard
If you feel like having 12 partitions on your SD card you can.
That leaves vold only handling the mounting of /media
This exists so that you can serve /media as USB Mass Storage.
You could have /media be a fixed mount by doing what you just did to the SD card.
The only hiccup there would be the Adobe Digital Editions wants to see /media as UMS.
Note: To edit init.rc, download bootutil from the signature, extract, edit and replace init.rc in uRamdisk.
Make sure that you have a backup and a recovery!
Note: All of the above changes to init.rc are wrong.
I can get it to mount in a shell, but not in init.rc
Whoops.
Oops, this thread has been forgotten.
Yes, auto-mounting ext3 SDcards has been solved.
See: http://forum.xda-developers.com/showthread.php?t=2184495
I want to be able to securely delete files(overwrite the whole file at least once) on my s3. I tried to install the app undelete which also has an option to securely delete files. But when I start the app it complains about not finding any fat formated file system. I also tried shredroid but this program crashes on startup, maybe because it also expects a fat file system? So is there a working way to secure delete files on the s3? It doesn't have to be an app, if there is some linux utility like srm compiled for android that would be great.
There's an app called Secure Deletion for Android in the Play Store that should do what you need. No free version, though, and it only has one review and 50+ downloads. FWIW, the single review was 5 stars. I'm gonna keep looking because I would like the same thing.
From what I can tell, stuff like that wont work on our devices' internal memory due to the method samsung has used to grant access to the partitions. Undelete never worked on my Xoom because of the same issue, possibly due to the fact both devices utilize MTP. However, it should work on any external SD cards you may have, however that is just me speculating as I have not tried it.
Sent from my SAMSUNG-SGH-I747 using xda premium
d3athsd00r said:
From what I can tell, stuff like that wont work on our devices' internal memory due to the method samsung has used to grant access to the partitions. Undelete never worked on my Xoom because of the same issue, possibly due to the fact both devices utilize MTP. However, it should work on any external SD cards you may have, however that is just me speculating as I have not tried it.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Now that you mention it, the internal storage is mounted as a FUSE filesystem, not the expected ext3/4, so it's probably because it's a "fake" filesystem. I wonder if there is a way to access the raw physical filesystem (/data is ext4, which should be compatible with most secure delete apps) instead of the userspace filesystem.
EndlessDissent said:
Now that you mention it, the internal storage is mounted as a FUSE filesystem, not the expected ext3/4, so it's probably because it's a "fake" filesystem. I wonder if there is a way to access the raw physical filesystem (/data is ext4, which should be compatible with most secure delete apps) instead of the userspace filesystem.
Click to expand...
Click to collapse
Thank you. Couldn't remember what it is called. But that is exactly the reason it can't find it with the app. Also, if journaling is enabled, then a secure delete still wont work on ext3/4. This isn't a bug, its due to the way ext with journaling handles reads/writes.
Sent from my SAMSUNG-SGH-I747 using xda premium
Anyone know why it's mounted via fuse? The same files are also available via /data/media and /data is mounted as ext4. Maybe it would be possible to unmount the fuse filesystem, remount the data filesystem as ext2 (no journaling) and then run some secure delete program?
octapod said:
Anyone know why it's mounted via fuse? The same files are also available via /data/media and /data is mounted as ext4. Maybe it would be possible to unmount the fuse filesystem, remount the data filesystem as ext2 (no journaling) and then run some secure delete program?
Click to expand...
Click to collapse
It's because of the MTP. If it were mounted as a normal filesystem, you could use USB Mass Storage, but you would lose access to all of your internal storage while it was in UMS mode.
Also, I don't think you can mount one filesystem as another, so mounting ext4 as ext2 will possibly corrupt your data. What you could do is mount the ext4 filesystem with the journal features turned off (which is practically the same as ext2 but better), then secure delete.
The issue for me is, that task seems a lot more involved on a phone/tablet than it is on an actual computer. Not sure if it would even work. And if you want to secure delete every time you delete something, that's a whole lot of effort to go through. Of course, if you want it deleted that badly, it's probably worth it to you.
Hey guys, for a couple reasons I'd like to be able to format my micro SD card with the ext4 file system.
I can format my card using a computer running Ubuntu, but the card will not mount.
I'm running CM10 on my P3113.
Is there any simple way to do this?
It seems like it'd be best to use vold to mount the sdcard, but that doesn't support ext4 I guess?
Just wondering...
Ext4 support has to come from kernel.
???
Literally every other mounted filesystem on the CM10 ROM I use is ext4...
I'm gonna try mounting via an init.d script.
We'll see if that works...
Solved this one, it was easier than I expected.
You need to format the card, and then mount it at boot via a script.
CM9 and 10 support init.d scripts, so I have a script file at /system/etc/init.d/95sdcardext4
with this contents:
Code:
#!/system/xbin/sh
# Mount SD Card Ext4 Script
mount -rw -t ext4 /dev/block/mmcblk1p1 /storage/sdcard1
This runs very early in the boot up process, and ext4 partitions mount basically instantly, so everything is working as expected so far.
More tests need to be done, but I'm fairly certain I can package this up in a flashable ZIP package.
Brilliant !
ext4 is anyways far better than fat32 except Windows/Mac compatibility.
Awaiting your stable work
It will work on a s5670 running cm10 jb4.1.1?
I just have to create a file with that lines and put it in /system/etc/init.d/95sdcardext4 ?????????
I cannot get link2sd to mount the ext4 partition.
Thx
DivinityCycle said:
Solved this one, it was easier than I expected.
You need to format the card, and then mount it at boot via a script.
CM9 and 10 support init.d scripts, so I have a script file at /system/etc/init.d/95sdcardext4
with this contents:
Code:
#!/system/xbin/sh
# Mount SD Card Ext4 Script
mount -rw -t ext4 /dev/block/mmcblk1p1 /storage/sdcard1
This runs very early in the boot up process, and ext4 partitions mount basically instantly, so everything is working as expected so far.
More tests need to be done, but I'm fairly certain I can package this up in a flashable ZIP package.
Click to expand...
Click to collapse
Sorry about that, I don't have one of these anymore. I had a P3113, but switched to a T869, which is a very similar device but has 4G and some different stuff going on under the hood.
My brief ext4 experiment was honestly not that big of a deal. I ended up going back to FAT32 because the benefits didn't outweigh the annoyances.
The biggest issue I had was I couldn't figure out how to make the file system permissions behave in the same highly permissive way that FAT32 does. I ran into several force closes and other things that resulted from apps not being to read / write stuff on the card that they should have been able to. I know you can CHMOD stuff, and a boot script could chmod everything on the card, but that seems like a bandaid.
Maybe there's a way to make the permissions behave a specific way via the mount parameters? I didn't investigate deeply enough because my life got busy, and during the changeover to the new tab it was just easier to go back to FAT32. Also my new tab has 16GB of internal storage, so I've been much less stressed about storage.
Ok folks.. ...reviving an ancient thread....from good ol days when it 'KISS' was common for Android.
What about android 7+ onward . All this stuff is deprecated. My 128gb is cut into 3 Ext4's.
(I need a journaled FS - that story a lil later )
I can mount easily but problem is apps cant see it and its all got to do with mount space concept.
I am Su'ed via Magisk
Can someone post a step by step guide to mount ext4 on 7+
I've given up on reformatting the internal memory as EXT4 (my last post). However now, I want to mount an external SD card that is EXT4 (or any file format that has UNIX permissions). I can't get my device to mount the card, it says the filesystem is unsupported. Now, that's bull**** since Android has built in support for EXT. After searching threads here on XDA and Google, and even purchasing EzyMount as recommended, I can't get it to mount. I've tried BusyBox and mount commands (as root), with various errors such as "mount operation not supported on transport endpoint". I'm at my wit's end by now, trying to get some filesystem which has support for symlinks and UNIX permissions... any ideas?
kcattakcaz said:
I've given up on reformatting the internal memory as EXT4 (my last post). However now, I want to mount an external SD card that is EXT4 (or any file format that has UNIX permissions). I can't get my device to mount the card, it says the filesystem is unsupported. Now, that's bull**** since Android has built in support for EXT. After searching threads here on XDA and Google, and even purchasing EzyMount as recommended, I can't get it to mount. I've tried BusyBox and mount commands (as root), with various errors such as "mount operation not supported on transport endpoint". I'm at my wit's end by now, trying to get some filesystem which has support for symlinks and UNIX permissions... any ideas?
Click to expand...
Click to collapse
you fully rooted with custom kernel or only with rdlv etc?
First you gotta figure out how to mount this damn thing, gotta be possible.
Then you need to get this done on bootup, either in init.rc or init.d or smth.
You probably just use wrong commands? But I could be wrong, didnt try that yet but would also be interested. Having the file permissions also on SD would be nice, but it could cause trouble with mtp maybe?
zroice said:
you fully rooted with custom kernel or only with rdlv etc?
First you gotta figure out how to mount this damn thing, gotta be possible.
Then you need to get this done on bootup, either in init.rc or init.d or smth.
You probably just use wrong commands? But I could be wrong, didnt try that yet but would also be interested. Having the file permissions also on SD would be nice, but it could cause trouble with mtp maybe?
Click to expand...
Click to collapse
I am rooted, but stock ROM and kernel. MTP is for connecting to a computer? If it is, I don't need that. I have tried
mount -rw -t ext4 /dev/block/mmcblk1p1 /storage/extStorageCard
and variants switching the flags and options.
Interesting... I just typed that command in to make sure I didn't make any typos.... and my phone crashed and rebooted. I typed it again to see if it would cause another crash and it appears to have mounted the card! Whwn I type "df" at the prompt it now shows a 28.6 GB filesystem at that location, which has to be my sd card.
Why, how, I don't know. It works, it's all I can say.