Remix OS live USB : OS partition, PLUS data partition visible on windows. - Remix OS for PC

Using a usb key for a live USB of remix os in the same time as a data external drive isn't possible actually due to windows not being able to see further than one partition on the stick (ok, except if we use remix os partition as the data one ... without accidentally messing it up, but looks like it has an automatic size and the place it uses limit us).
I remember I had a similar problem with one of my first Linux live too. Not sure how I dealt with it but I were able to end having both after some search and understanding : liveOS partition, and a data partition visible on Windows (no problem like this with a Linux).
I'll try to reproduce with a linux if I have the time but here is what I'm looking for :
Ooops, since I can't post links nor upload images, I put the image link as my twitter in my profile
So, won't the data partition be ok to use on windows if like on 2nd example, the live os isn't installed in the same place as in the 1rst one ? I already tried to prepare 2 partitions before using the installation tool and choose the one destined for remixOS (and only visible) to install on it but the tool always end wiping ALL the key, and then partitioning appears to be the same.
Can pass through this problem be done by the tool ? (being able to install NEXT to a data partition to keep it visible by windows, or hide remixOS ones)
I ideally need this key for both usages, and if it's possible I think I'm not alone.
Does this can be added ?

---

@Esdeve
The reason you don't see the partitions in Windows is because they are in EXT4 filesystem, but I guess u know that already .
There are few software solutions for mounting these, but it will only mount the whole Remix system partiton, not the "partition inside the partition".
So basically it'll mount the partition with data.img (remix data partition), inird, ramdisk.... But not the data.img itself.
I don't think it's possible too easily and quickly make this automatic. Even on Linux u'd have to set up data.img to be automatically mounted when pendrive is detected.
Using the official .iso to USB installer won't allow you do what you need, but you can boot Linux on ur PC and with gParted extend/shrink existing USB partitions and maybe make a new one for other purposes.
Sent from mobile

---

Yup. Know that. I think you didn't understood what I'm looking to do ... but I may express poorly in english when speaking about computing subjects. Or I may not understand myself what you are answering too ^^'
Here we re-go : I'm looking to have both a data partition and the two partitions of RemixOS which are a Fat32 and an Ext one. I don't need having an access to the Ext, and I don't want to use the Fat32 one as a data partition because it's the OS partition, it's unsafe to use it for this, I may mess with it accidentally.
I don't need to modify the sizes of any partitions (from a Linux or not) since installation leaves room to be used. But since the fat32 already exists, I basically can't create/keep a 2nd fat/fat32/NTFS one next to it, this is no use, windows won't see it, the fat32 from remixOS is first, so Windows only sees this one and not my own, and I can't change that with the way the installation is made. Moving the two RemixOS partitions is of course totally excluded and will render the os unable to boot so I won't try it except maybe if able to do #3.
Solutions ?
1 - Being able to do what I just proposed in 1rst post : have the devs make the installer able to install in place of a designated partition (and not on all the key), in the right part of what is displayed in he graphic from my partition software, leaving the possibility to create afterward a fat/fat32/ntfs partition to the left, and seen by windows instead of the remixOS's fat32 without destroying the boot ... Uh, if that does the trick, I didn't experiment this sort of things a lot but I'm sure I succeeded with a live persistent linux once.
2 - RemixOS installer may only use EXT partitions and no fat32 ? Can't it ? Leaving windows readable formats free to use for something else.
3 - I'm planing to move the partitions like needed (there I know I'll be able to access my personal data partition I created), and then try some Grub thing on my key to keep the live system bootable, but I'm not sure to remember how to, nor if this will work, nor even if grub can launch RemixOS.
Well. I'd add to all this that I'm not specially searching for help, I know actually except for the complex solution #3, that it's impossible to manage what I need. It's more like an asking/proposing of feature/possibility. And I'm pretty sure I won't be the only one to think it's waste to use my 3.0 stick rendering it unable to serve in the same time for portable data storage when it always have loooots of place.
I read in the ask/propose feature part of the devs site to come post her ... So I did. But there is no "evolution" section and only a device classifying here. So here I wrote. Sorry if misunderstood.

---

The problem with what you wrote is that you overcomplicate it. Keep it simple and short - that's best.
Did understood correctly that you want to use the USB as Remix Live Stick and as a typical storage device?
Did you read my whole post?
Remix when installed on USB should use all it's space - makes 3 partitions:
1. Boot
2. System
3. Data for external storage purposes.
The 3rd is what you see in Windows.
All you need to do now is just to adjust sizes of other partitions (it's possible without corrupting existing files), but hard to do under Windows. Then u need to expand this 3rd partition.
Sent from mobile

---

Sorry ^^' I know I use too much words, but it appears I can't make simple when speaking about technical matters, and in a language I'm not used to resume tech things.
Of course, I read your posts. I"m on a 32gb stick. I can see 3 partitions :
1 : REMIX_OS (apparently data, since it's the only one I can access from windows). Fat32. 7.64Gb sized.
2 : REMIXOSSYS. Fat32 too. But not accessible from windows (I understand this like it's because it's 2nd principal partition, so windumbOS doesn't see it). 5Gb sized. Part of the system. including the boot isn't it ?
3 : Third partition. System. Format unknown from Windows or either with Linux (using gParted). Named "unknown". And takes full remnants of the stick capacity (16Gb). Does it needs theses 16Gb from the start ? Apparently not obligatory since looking at the space used from the live OS, seems doesn't uses it a lot compared to the available place.
This last one is the main problem for me. I don't see how to treat this "other" partition, and at start, then reading your 1/2/3 list, I believed that was this one used as "data". I understand well there are ext partitions within since the os is an unix, but I don't see the whole as an EXT partition, whenever I'm on Windows or Linux, so with my knowledge and capacities, I can't access nor reduce it.
Will try command line or to find a similar problem with solution, but I think this won't change lot here. About the two Fat32, I'm not really confident about what you said and the possibility of moving the whole, and especially theses two. Systems and boots don't like this, they don't find each others well afterward ^^ don't they ? Resizing the two first without moving ? Ok. But that will just make me room for two new small useless partitions between the three others, and I strongly believe windows won't see em but only the "REMIX_OS" one.
If possible, I'm going to try another way to obtain live remixOS usb too. Can't unetbootin or such do the job ?
If the choice of having data at the beginning isn't technical, can't the devs make the installation create the data partition at the end instead, plus add an option advising a minimal space for the "unknown" partition and letting users chose what size it will be ?

---

Esdeve said:
Sorry ^^' I know I use too much words, but it appears I can't make simple when speaking about technical matters, and in a language I'm not used to resume tech things.
Of course, I read your posts. I"m on a 32gb stick. I can see 3 partitions :
1 : REMIX_OS (apparently data, since it's the only one I can access from windows). Fat32. 7.64Gb sized.
2 : REMIXOSSYS. Fat32 too. But not accessible from windows (I understand this like it's because it's 2nd principal partition, so windumbOS doesn't see it). 5Gb sized. Part of the system. including the boot isn't it ?
3 : Third partition. System. Format unknown from Windows or either with Linux (using gParted). Named "unknown". And takes full remnants of the stick capacity (16Gb). Does it needs theses 16Gb from the start ? Apparently not obligatory since looking at the space used from the live OS, seems doesn't uses it a lot compared to the available place.
This last one is the main problem for me. I don't see how to treat this "other" partition, and at start, then reading your 1/2/3 list, I believed that was this one used as "data". I understand well there are ext partitions within since the os is an unix, but I don't see the whole as an EXT partition, whenever I'm on Windows or Linux, so with my knowledge and capacities, I can't access nor reduce it.
Will try command line or to find a similar problem with solution, but I think this won't change lot here. About the two Fat32, I'm not really confident about what you said and the possibility of moving the whole, and especially theses two. Systems and boots don't like this, they don't find each others well afterward ^^ don't they ? Resizing the two first without moving ? Ok. But that will just make me room for two new small useless partitions between the three others, and I strongly believe windows won't see em but only the "REMIX_OS" one.
If possible, I'm going to try another way to obtain live remixOS usb too. Can't unetbootin or such do the job ?
If the choice isn't technical, can't the devs make the installation create the data partition at the end instead of the beginning, plus add an option advising a minimal space for the "unknown" partition and letting users chose what size it will be ?
Click to expand...
Click to collapse
The unknown should be ext4 userdata mounted as /data and RemixOSSys should only contain system
Can you post a screenshot of the contents of Remix_OS and within RemixOS check mount and df to check what's mounted where.

---

About the two command lines from within remixOS. I don't know how to copy it or save it to a file. Looks like shortcuts/commands I'm used to aren't suited here (tried to use "script" and "-l > /path/to/file.txt". Either end up with a file protected in writing, or path not existing, maybe even command not existing answers). So how do I do that ? Or maybe where will I be enabled to create a .txt from the terminal ?

---

Esdeve said:
About the two command lines from within remixOS. I don't know how to copy it or save it to a file. Looks like shortcuts/commands I'm used to aren't suited here (tried to use "script" and "-l > /path/to/file.txt". Either end up with a file protected in writing, or path not existing, maybe even command not existing answers). So how do I do that ? Or maybe where will I be enabled to create a .txt from the terminal ?
Click to expand...
Click to collapse
You should be able to redirect to sdcard:
mount > /sdcard/mount.txt
df >> /sdcard/mount.txt

---

Hmm..
If you don't wish Windows to have access to your usb stick...
Use "diskmanager" and remove the drive letter
Cheers

---

@mitchell4you : That's not what I propose.
@HypoTurtle, and to recapitulate for anyone about screenshots :
Since I can't post links for the moment, I put the screens links in my profile in place of contact infos. I'll modify my posts later when I'll own the rights.
Twitter is for the first post of the thread.
G+ is the Remix_OS partition screen you asked for.
Say if other partition screenshot is needed.
Next are the command lines ...
Mount :
tmpfs on / type tmpfs (ro,relatime)
/dev/loop1 on /system type ext4 (ro,relatime,data=ordered)
/dev/block/sdb3 on /data type ext4 (rw,noatime,nodiratime,data=ordered)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime,mode=755)
none on /acct type cgroup (rw,relatime,cpuacct)
none on /sys/fs/cgroup type tmpfs (rw,relatime,mode=750,gid=1000)
tmpfs on /mnt type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
pstore on /sys/fs/pstore type pstore (rw,relatime)
none on /cache type tmpfs (rw,nosuid,nodev,noatime)
tmpfs on /storage type tmpfs (rw,relatime,mode=755,gid=1000)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,relatime)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
/dev/fuse on /mnt/runtime/default/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/block/vold/public:8_1 on /mnt/media_rw/E45C9A015C99CF24 type fuseblk (rw,dirsync,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/fuse on /mnt/runtime/default/E45C9A015C99CF24 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/E45C9A015C99CF24 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/E45C9A015C99CF24 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/E45C9A015C99CF24 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/block/vold/public:8_2 on /mnt/media_rw/01D0A77D0C4455E0 type fuseblk (rw,dirsync,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/fuse on /mnt/runtime/default/01D0A77D0C4455E0 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/01D0A77D0C4455E0 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/01D0A77D0C4455E0 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/01D0A77D0C4455E0 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/block/vold/public:8_3 on /mnt/media_rw/720ddd36-a9a5-4e8d-a80f-bf25799d1fc7 type ext4 (rw,dirsync,nosuid,nodev,noatime,data=ordered)
/dev/fuse on /mnt/runtime/default/720ddd36-a9a5-4e8d-a80f-bf25799d1fc7 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/720ddd36-a9a5-4e8d-a80f-bf25799d1fc7 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/720ddd36-a9a5-4e8d-a80f-bf25799d1fc7 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/720ddd36-a9a5-4e8d-a80f-bf25799d1fc7 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/block/vold/public:8_5 on /mnt/media_rw/7326C07B75B67850 type fuseblk (rw,dirsync,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/fuse on /mnt/runtime/default/7326C07B75B67850 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/7326C07B75B67850 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/7326C07B75B67850 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/7326C07B75B67850 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/block/vold/public:8_7 on /mnt/media_rw/288A9EF38A9EBCAE type fuseblk (rw,dirsync,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/fuse on /mnt/runtime/default/288A9EF38A9EBCAE type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/288A9EF38A9EBCAE type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/288A9EF38A9EBCAE type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/288A9EF38A9EBCAE type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/block/vold/public:8_8 on /mnt/media_rw/01D0A77D072BDC90 type fuseblk (rw,dirsync,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/fuse on /mnt/runtime/default/01D0A77D072BDC90 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/01D0A77D072BDC90 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/01D0A77D072BDC90 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/01D0A77D072BDC90 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/block/vold/public:8_17 on /mnt/media_rw/3834-74A4 type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/fuse on /mnt/runtime/default/3834-74A4 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/3834-74A4 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/3834-74A4 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/3834-74A4 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/block/vold/public:8_18 on /mnt/media_rw/C004-4EFA type vfat (rw,nosuid,nodev,noexec,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/fuse on /mnt/runtime/default/C004-4EFA type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/C004-4EFA type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/C004-4EFA type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/C004-4EFA type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
And df :
Filesystem-----------------------------1K-blocks-----Used-------Available-----Use%----Mounted on
tmpfs--------------------------------4012216--------3304-------4008912-------1%--------/
/dev/loop1--------------------------2539312-------1962424----576888-------78%------/system
/dev/block/sdb3------------------16382888-----1212340-----15170548------8%-------/data
tmpfs--------------------------------4012216--------76-----------4012140-------1%--------/dev
none---------------------------------4012216--------12------------4012204------1%--------/sys/fs/cgroup
tmpfs--------------------------------4012216--------0-------------4012216------0%-------/mnt
none---------------------------------4012216--------0-------------4012216------0%-------/cache
/dev/fuse---------------------------16382888------1212340-----15170548----8%-------/mnt/runtime/default/emulated
/dev/fuse---------------------------16382888------1212340-----15170548----8%-------/mnt/runtime/read/emulated
/dev/fuse---------------------------16382888------1212340-----15170548----8%-------/mnt/runtime/write/emulated
/dev/block/vold/public:8_1----102396---------28804-------73592--------29%-----/mnt/media_rw/E45C9A015C99CF24
/dev/fuse---------------------------102396---------28804-------73592--------29%-----/mnt/runtime/default/E45C9A015C99CF24
/dev/fuse---------------------------102396---------28804-------73592--------29%-----/mnt/runtime/read/E45C9A015C99CF24
/dev/fuse---------------------------102396---------28804-------73592--------29%-----/mnt/runtime/write/E45C9A015C99CF24
/dev/block/vold/public:8_2----297780836----115267204--182513632---39%----/mnt/media_rw/01D0A77D0C4455E0
/dev/fuse----------------------------297780836---115267204---182513632---39%---/mnt/runtime/default/01D0A77D0C4455E0
/dev/fuse----------------------------297780836---115267204---182513632---39%---/mnt/runtime/read/01D0A77D0C4455E0
/dev/fuse----------------------------297780836---115267204---182513632---39%---/mnt/runtime/write/01D0A77D0C4455E0
/dev/block/vold/public:8_3-----92798268----4900736-----87897532---6%----/mnt/media_rw/720ddd36-a9a5-4e8d-a80f-bf25799d1fc7
/dev/fuse-----------------------------92798268----4900736-----87897532---6%----/mnt/runtime/default/720ddd36-a9a5-4e8d-a80f-bf25799d1fc7
/dev/fuse-----------------------------927982686---4900736----87897532---6%----/mnt/runtime/read/720ddd36-a9a5-4e8d-a80f-bf25799d1fc7
/dev/fuse-----------------------------92798268-----4900736----87897532---6%----/mnt/runtime/write/720ddd36-a9a5-4e8d-a80f-bf25799d1fc7
/dev/block/vold/public:8_5-----12584956------256216------12328740----3%---/mnt/media_rw/7326C07B75B67850
/dev/fuse-----------------------------12584956-----256216-------12328740----3%--/mnt/runtime/default/7326C07B75B67850
/dev/fuse-----------------------------12584956-----256216-------12328740----3%--/mnt/runtime/read/7326C07B75B67850
/dev/fuse-----------------------------12584956-----256216-------12328740----3%--/mnt/runtime/write/7326C07B75B67850
/dev/block/vold/public:8_7------94412796-----61516412-----32896384--66%-/mnt/media_rw/288A9EF38A9EBCAE
/dev/fuse-----------------------------94412796-----61516412-----32896384---66%-/mnt/runtime/default/288A9EF38A9EBCAE
/dev/fuse-----------------------------94412796-----61516412-----32896384---66%-/mnt/runtime/read/288A9EF38A9EBCAE
/dev/fuse-----------------------------94412796-----61516412-----32896384---66%-/mnt/runtime/write/288A9EF38A9EBCAE
/dev/block/vold/public:8_8------220676840---183026824--37650016---83%--/mnt/media_rw/01D0A77D072BDC90
/dev/fuse-----------------------------220676840---183026824---37650016---83%--/mnt/runtime/default/01D0A77D072BDC90
/dev/fuse-----------------------------220676840---183026824---37650016---83%--/mnt/runtime/read/01D0A77D072BDC90
/dev/fuse-----------------------------220676840---183026824---37650016---83%--/mnt/runtime/write/01D0A77D072BDC90
/dev/block/vold/public:8_17-----7993744------68-------------7993676----1%----/mnt/media_rw/3834-74A4
/dev/fuse-----------------------------7993744------68-------------7993676-----1%---/mnt/runtime/default/3834-74A4
/dev/fuse-----------------------------7993744------68-------------7993676-----1%---/mnt/runtime/read/3834-74A4
/dev/fuse-----------------------------7993744------68-------------7993676-----1%---/mnt/runtime/write/3834-74A4
/dev/block/vold/public:8_18----5230592-------1178680------4051912-----23%--/mnt/media_rw/C004-4EFA
/dev/fuse-----------------------------5230592-------1178680------4051912-----23%--/mnt/runtime/default/C004-4EFA
/dev/fuse-----------------------------5230592-------1178680------4051912-----23%--/mnt/runtime/read/C004-4EFA
/dev/fuse-----------------------------5230592-------1178680---4051912--------23%--/mnt/runtime/write/C004-4EFA