The above thread concludes with BrainSlayer commenting:
BrainSlayer wrote:
the jffs storage is calculated by available flash space on the internal flash memory. now you mounted usb drive to /jffs. so its logic that such strange values are displayed. its not the internal flash memory which is supposed to be used for /jffs. for custom other drives you may use /mmc or /usr/local or even /opt. custom hacks are not considered by the gui
All well and good. But what does it mean when you DONT mount a USB partition to /jffs and it's STILL reported exabytedly wrong.
Now, to avoid the gparted bug where ext2 partitions are erroneously reported as ext4 by DD-WRT I'm using MiniTool Partition Wizard to partition the drive.
In this example I've created a stack of partitions (1g+1.9g+2g+2.1g+3g+4G+rest) to test my obversions - only 2GB partitions are reported incorrectly.
Posted: Wed Oct 12, 2022 15:15 Post subject: Re: USB partitions reported in exabytes BUG
egosumumbravir wrote:
Now, to avoid the gparted bug where ext2 partitions are erroneously reported as ext4 by DD-WRT I'm using
i've noticed dd-wrt report partition types incorrectly for years now, and just learned to ignore it.
but are you saying that the problem isn't with dd-wrt, but that there is a bug in gparted that if it is used to create the partitions, then dd-wrt will report the type incorrectly?
Posted: Thu Oct 13, 2022 3:48 Post subject: Re: USB partitions reported in exabytes BUG
MuzzleVelocity wrote:
but that there is a bug in gparted that if it is used to create the partitions, then dd-wrt will report the type incorrectly?
My findings
gparted bootable USB (v1.3.1-1-amd64): ext2 partitions are reported by the GUI as ext4. Even after refomatting via the gui. mkfs (at least I think it was mkfs) at the command line did correctly show them as ext2.
MiniTool Partition Wizard (v12.6): ext2 partitions are reported correctly as ext2.
Joined: 26 Mar 2013 Posts: 1857 Location: Hung Hom, Hong Kong
Posted: Fri Oct 14, 2022 4:32 Post subject:
egc wrote:
All routers only have ext4.ko which is compatible with ext2.
ext4 and ext3 are basically ext2 with journal. ext2 tools possibly could mount ext4 partitions, as long as you do NOT write to the partition, thus destroying synchronization with its journal. But then you might be able to repair the journal... never tried that.
And Window$ could possibly read ext2 and hence ext4 file systems using explore2fs. There are other methods of course, especially for Window$ 10/11.
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Fri Oct 14, 2022 10:37 Post subject:
While this topic has been semi answered still would like to see the USB tab full page screenshot just out of pure curiosity.
As for space, BS explains how the calculations work, in this case I suspect since drives mounted to /tmp, it's available space is equal to device free/available RAM.
If I were the OP my attempt would be to mount the drives as /mmc or /usr/local or /opt and see if this improves as suggested by BS and if not then perhaps he will rework and fix the issues.
Most of these DD-WRT areas range from 10 to 15/16 years old and have remained largely unchanged, things were just done/implemented that long ago drives weren't as large as today.
As for space, BS explains how the calculations work, in this case I suspect since drives mounted to /tmp, it's available space is equal to device free/available RAM.
Then I must ask - why is it only a 2.00Gb partition that is shown incorrectly when they're ALL mounted to /tmp/mnt (or indeed anywhere else not /jffs)?
1.99Gb and 2.01Gb are reported fine - as are other sizes. 2.00Gb is causing a problem somewhere.
Sadly, I've already deployed the testbench elsewhere offsite along with the USB stick. Will endeavour to remember to grab screenshots next time I can take it offline long enough to have a play.
