I think that gets off point..
Hosting Providers all provide 'different' services and limitations..
Other than the fact that their 'automated' systems are geared for ext4,
are they a 'good' hosting company?
I believe the criteria is meant to be things like..
* Good and Timely Support
* Maintaining a clean network
* Addressing Abuse complaints in a time fashion
And not the technical offerings.. eg we aren't going to compare those
who offer Linux Hosting vs Windows Hosting..
Are the good netizens and good partners to work with is what we are
looking for, and there are thousands of 'small' operators that also
probably fit in that category, but the larger ones have no excuse not to
be..
It sure isn't Eonix/ServerHub ;)
(Sorry, had to get one dig in, happy Monday)
23.231.108.2 (M) 82 iygknvdndc.insurancewhileyoulive.com
23.231.108.3 (M) 82 ctgqkilgax.insurancewhileyoulive.com
23.231.108.4 (M) 85 xaawmhxeob.insurancewhileyoulive.com
23.231.108.5 (M) 87 xajrkhpibc.insurancewhileyoulive.com
23.231.108.6 (M) 80 jnqqznptkg.insurancewhileyoulive.com
23.231.108.7 (M) 83 wgaryxvfds.insurancewhileyoulive.com
23.231.108.8 (M) 83 cffwsmeqnm.insurancewhileyoulive.com
23.231.108.9 (M) 87 lgbwxoxqsn.insurancewhileyoulive.com
23.231.108.10 (M) 88 edetgapxai.insurancewhileyoulive.com
23.231.108.11 (M) 87 guzzpbnytc.insurancewhileyoulive.com
23.231.108.12 (M) 85 yobqbmxtbc.insurancewhileyoulive.com
23.231.108.13 (M) 87 rggyakjgic.insurancewhileyoulive.com
23.231.108.14 (M) 84 gmjnvrjpli.insurancewhileyoulive.com
23.231.108.15 (M) 80 poiwndphuv.insurancewhileyoulive.com
23.231.108.16 (M) 90 drjoujcuii.insurancewhileyoulive.com
23.231.108.17 (M) 84 rtviwzdmnl.insurancewhileyoulive.com
23.231.108.18 (M) 84 rvygeyczev.insurancewhileyoulive.com
23.231.108.19 (M) 83 bzmthaybzb.insurancewhileyoulive.com
23.231.108.20 (M) 82 inglsqmvgp.insurancewhileyoulive.com
23.231.108.21 (M) 83 mcejvpiuzi.insurancewhileyoulive.com
23.231.108.22 (M) 84 oosbpadeft.insurancewhileyoulive.com
23.231.108.23 (M) 87 jokjinrvuu.insurancewhileyoulive.com
23.231.108.24 (M) 83 ftsyzegoyt.insurancewhileyoulive.com
23.231.108.25 (M) 86 xipqsqwhxo.insurancewhileyoulive.com
23.231.108.26 (M) 84 sjglgbpogh.insurancewhileyoulive.com
23.231.108.27 (M) 83 pozokhsryc.insurancewhileyoulive.com
23.231.108.28 (M) 85 wexvnywpjl.insurancewhileyoulive.com
23.231.108.29 (M) 84 widojojjnf.insurancewhileyoulive.com
23.231.108.30 (M) 6 paovmgfqwu.insurancewhileyoulive.com
23.231.108.31 (M) 5 sdenzytejm.insurancewhileyoulive.com
23.231.108.33 (M) 82 omcuzwqukw.insurancewhileyoulive.com
23.231.108.34 (M) 87 zlgjpveads.advancedtechmedia.com
23.231.108.35 (M) 81 qorzskpoay.advancedtechmedia.com
23.231.108.36 (M) 85 kazawffxah.advancedtechmedia.com
23.231.108.37 (M) 84 vlwulnbybq.advancedtechmedia.com
23.231.108.38 (M) 89 ogsycxojfw.advancedtechmedia.com
23.231.108.39 (M) 82 vvruglfsqv.advancedtechmedia.com
23.231.108.40 (M) 85 mcrubfuzov.advancedtechmedia.com
23.231.108.41 (M) 85 yykjdviwsd.advancedtechmedia.com
23.231.108.42 (M) 87 ihzrfvdygo.advancedtechmedia.com
23.231.108.43 (M) 84 fsqxshsiza.advancedtechmedia.com
23.231.108.44 (M) 84 lzpxxoraua.advancedtechmedia.com
23.231.108.45 (M) 83 emojnnxgzc.advancedtechmedia.com
23.231.108.46 (M) 81 tleqnyhvvg.advancedtechmedia.com
23.231.108.47 (M) 83 dfwxpwjmqe.advancedtechmedia.com
23.231.108.48 (M) 86 efgkugtjzq.advancedtechmedia.com
23.231.108.49 (M) 86 zdrapibafs.advancedtechmedia.com
23.231.108.50 (M) 84 zflbpfpzbg.advancedtechmedia.com
23.231.108.51 (M) 84 dipsegtols.advancedtechmedia.com
23.231.108.52 (M) 86 sdlxjwamqf.advancedtechmedia.com
23.231.108.53 (M) 87 irwnfnctmp.advancedtechmedia.com
23.231.108.55 (M) 84 nzufhniavq.advancedtechmedia.com
23.231.108.56 (M) 85 rceivnsjgd.advancedtechmedia.com
23.231.108.57 (M) 81 szoynvmqjn.advancedtechmedia.com
23.231.108.58 (M) 86 wtvbkoyxsr.advancedtechmedia.com
23.231.108.59 (M) 84 jqkfomjatk.advancedtechmedia.com
23.231.108.60 (M) 85 cujtytqkuh.advancedtechmedia.com
23.231.108.61 (M) 81 jgjpppefvc.advancedtechmedia.com
23.231.108.62 (M) 82 tdixnghkuj.advancedtechmedia.com
On 2021-02-22 7:48 a.m., Mary via mailop wrote:
You are both dancing around a very serious issue by providing excuses and
irrelevant facts.
Did you know that Linode hides the fact that they only support ext4? A serious
limitation for a cloud provider and something that should be mentioned in their
home page, in bold letters.
There are tons of services and APIs that fail to work, for example:
- shrink a partition
- grow a partition
- automatic repartition after server upgrade
- all backups
- the network helper
- all API file access
What is worrisome, is how they've gone into great measures to hide this serious
limitation, none of their installation procedures warns you of the above issues
and there is no warning that their installation images have been modified to
REMOVE the default file system and replace it with ext4.
(I verified all of the above about 5-6 months ago, so its possible something
may have changed since then, but I doubt it)
On Sun, 21 Feb 2021 21:41:44 +0000 Steve Holdoway via mailop
<mailop@mailop.org> wrote:
Oh dear,
/dev/nvme2n1 on /data/mongodb type ext4 (rw,noatime)
( yeah I only run it on ec2 ) but not a word of complaint.
https://scalegrid.io/blog/xfs-vs-ext4-comparing-mongodb-performance-on-aws-ec2
Given average performance of linode disks - not a complaint, I'm a happy linode
user - switching to XFS would make minimal, if any difference. Plus the fact
that the only file system I've ever had spontaneously explode on me is... you
guessed it, XFS!
Steve
February 22, 2021 9:08 AM, "Grant Taylor via mailop" <mailop@mailop.org> wrote:
On 2/21/21 1:58 AM, Mary via mailop wrote:
They only support the ext4 file system.
I feel like that's poorly worded. Or at least a victim of semantics.
"support" equates to hand holding and tooling. Their kernels do include
support (as in capability) for many file systems.
myLinode$ fgrep -v "nodev" /proc/filesystems
reiserfs
ext3
ext2
ext4
cramfs
squashfs
vfat
exfat
iso9660
romfs
fuseblk
udf
jfs
xfs
gfs2
gfs2meta
btrfs
All their servers get installed with ext4 by default.
"by default" being the operative phrase.
If you manually format into something else (xfs, btrfs, etc) then most
(all?) linode services stop working, like their backups!
I don't know about this. I've had mixed results over the last five years.
Maybe its ok for most use cases, but things like MongoDB will complain
if run on ext4.
It's trivial to add an additional disk to the Linode. Use a file system
that MongoDB is more happy with and leave the root file system the
default (ext4) if you want to use Linode's ""features. (I avoid them.)
--
Grant. . . .
unix || die
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
--
"Catch the Magic of Linux..."
------------------------------------------------------------------------
Michael Peddemors, President/CEO LinuxMagic Inc.
Visit us at http://www.linuxmagic.com @linuxmagic
A Wizard IT Company - For More Info http://www.wizard.ca
"LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd.
------------------------------------------------------------------------
604-682-0300 Beautiful British Columbia, Canada
This email and any electronic data contained are confidential and intended
solely for the use of the individual or entity to which they are addressed.
Please note that any views or opinions presented in this email are solely
those of the author and are not intended to represent those of the company.
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
