I'm not sure that all SSDs should only be used with ext2. Early/cheaper
JMicron-based SSDs have lots of issues with small writes which can cause
big slowdowns, and certainly journalling wouldn't help for that. But
there are now several drives that dont have anywhere near the same
performance proble
I'm not sure that it would do anything but confuse the user, Dimitrios.
You and I obviously know whether we have an SSD, but I don't think most
people are aware of anything about their hard drive but the storage
space -- I mean, 5400-RPM hard drives continue to exist and are even
sold with Intel Co
Workaround for Jaunty: add the kernel parameter
"partman/default_filesystem=ext2" when booting the installer.
There is other work in progress on detecting SSDs.
--
Incorrect partition creation when on an SSD (EXT3 instead of EXT2)
https://bugs.launchpad.net/bugs/281683
You received this bug noti
ok, here's just an idea:
what if, as a temporary solution, we add one more choice in the installer's
partitioner?
something like "Guided - Flash/SSD media - use entire disk"...
until we find a way to detect the type of media, that is...
--
Incorrect partition creation when on an SSD (EXT3 instea
on one hand, using hdparm (or sdparm) might bring us closer to a solution
however, we definitely cannot depend on the model number for reliable detection
(possibility of false negatives, and maybe even some false positives???)
--
Incorrect partition creation when on an SSD (EXT3 instead of EXT2)
Similar on this Acer Aspire One:
sudo hdparm -I /dev/sda | grep Model
Model Number: P-SSD1800
...if this is useful
--
Incorrect partition creation when on an SSD (EXT3 instead of EXT2)
https://bugs.launchpad.net/bugs/281683
You received this bug notification because you are a memb
Colin: ad detection of SSD - in my eee 901 it's shown in hdparm:
$ sudo hdparm -I /dev/sda | grep Model
Model Number: ASUS-PHISON SSD
OTOH dmesg doesn't show any SSD-specific messages...
ad settings for SSD: I'd vote for mount -o noatime,commit=60 and
vm.swappiness=0
vm.dirty_backg
thanks colin.
james said he chose guided, not manual.
--
Incorrect partition creation when on an SSD (EXT3 instead of EXT2)
https://bugs.launchpad.net/bugs/281683
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
(Marking as low simply because I'm not sure whether we'll get to this
any time soon. It seems that manual partitioning is the most practical
solution for the time being. I'm interested in how you got confused when
trying to choose ext2 instead; it ought to be fairly straightforward in
the manual pa
Being able to detect it would make it relatively straightforward to fix
in the manual partitioner. It'd still be an utter pain in the automatic
partitioner because ext3 is hardcoded in the recipe files. I'm not even
sure where to start here ...
** Changed in: partman-partitioning (Ubuntu)
Sourcepa
now we need to see if there's actually a way to tell if the underlying
storage device is magnetic or solid state...
** Changed in: ubiquity (Ubuntu)
Sourcepackagename: None => ubiquity
Status: Incomplete => New
--
Incorrect partition creation when on an SSD (EXT3 instead of EXT2)
https://
I chose "guided".
And yes, my suggestion is that the Ubuntu installer automatically uses
EXT2 when installing to an SSD - rather, that its choice of EXT3 for an
SSD is incorrect.
--
Incorrect partition creation when on an SSD (EXT3 instead of EXT2)
https://bugs.launchpad.net/bugs/281683
You rece
just to clarify: your suggestion is that the ubuntu installer
automatically uses ext2 when installing to an ssd?
also, during installation, which method of formatting did you choose?
(manually, guided, etc)
** Changed in: ubuntu
Status: New => Incomplete
--
Incorrect partition creation w
13 matches
Mail list logo
