Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #264691
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: raid10 is killing me, and applications that aren't willing towait for it to respond |
| Date | 2023-12-13 19:20 +0100 |
| Message-ID | <HKBZT-dlS9-3@gated-at.bofh.it> (permalink) |
| References | <HKzlo-dkig-37@gated-at.bofh.it> <HKzEK-dkp4-17@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 12/13/23 10:41, Tom Furie wrote:
> gene heskett <gheskett@shentel.net> writes:
>
>> I thought I was doing things right a year back when I built a raid10
>> for my /home partition. but I'm tired of fighting with it for
>> access. Anything that wants to open a file on it, is subjected to a
>> freeze of at least 30 seconds BEFORE the file requester is drawn on
>> screen. Once it has done the screen draw and the path is established,
>
> Where is the raid10 located and how is it interfaced to the device
> you're accessing it from? That delay, along with other things you
> mentioned suggests (but this is only a guess without other relevant
> information) a DNS timeout.
>
It is a separate 6 port sata controller because the mobo is out of
ports. There is no obvious lag during bios post or grub booting it.
/etc/fstab:
gene@coyote:/etc/lvm/profile$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=f295334b-fdcb-4428-bed3-cb9e9e129be6 / ext4
errors=remount-ro 0 1
# /tmp was on /dev/sda3 during installation
UUID=518cb65d-21f0-493f-8bb5-a5f435796991 /tmp ext4
defaults 0 2
# swap was on /dev/sda2 during installation
UUID=422b50db-9913-4ed3-92c3-dc18be72cc61 none swap sw
0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
UUID=bc6135de-0578-4e3b-b2c0-5c4687abd9bd /home ext4
errors=remount-ro 0 2
UUID=d24c3a99-9f40-4b71-92d4-916804553cb5 none swap sw
0 0
-----------------------------
From df:
gene@coyote:/etc/lvm/profile$ sudo df
[sudo] password for gene:
Filesystem 1K-blocks Used Available Use% Mounted on
udev 16328024 0 16328024 0% /dev
tmpfs 3272676 1876 3270800 1% /run
/dev/sda1 863983352 18784928 801236776 3% /
tmpfs 16363376 12 16363364 1% /dev/shm
tmpfs 5120 8 5112 1% /run/lock
/dev/sda3 47749868 222628 45069232 1% /tmp
/dev/md0p1 1796382580 330887008 1374170596 20% /home
tmpfs 3272672 45868 3226804 2% /run/user/1000
-----------------------------
A dhcpd has been installed, but is limited to issuing a single fixed
address to a 3d printer plugged into my network, as the printer doesn't
seem to know what to do with a hosts file that runs the rest of my home
network. Anything else you want, just ask.
> Cheers,
> Tom
>
> .
Thank you Tom.
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
raid10 is killing me, and applications that aren't willing to wait for it to respond gene heskett <gheskett@shentel.net> - 2023-12-13 16:30 +0100
Re: raid10 is killing me, and applications that aren't willing to wait for it to respond Tom Furie <tom@furie.org.uk> - 2023-12-13 16:50 +0100
Re: raid10 is killing me, and applications that aren't willing towait for it to respond gene heskett <gheskett@shentel.net> - 2023-12-13 19:20 +0100
Re: raid10 is killing me, and applications that aren't willing towait for it to respond Tom Furie <tom@furie.org.uk> - 2023-12-13 20:00 +0100
Re: raid10 is killing me, and applications that aren't willingtowait for it to respond gene heskett <gheskett@shentel.net> - 2023-12-13 20:30 +0100
Re: raid10 is killing me, and applications that aren't willing to wait for it to respond Pocket <pocket@columbus.rr.com> - 2023-12-13 18:00 +0100
Re: raid10 is killing me, and applications that aren't willing towait for it to respond gene heskett <gheskett@shentel.net> - 2023-12-13 19:30 +0100
Re: raid10 is killing me, and applications that aren't willing towait for it to respond Nicolas George <george@nsup.org> - 2023-12-13 19:50 +0100
Re: raid10 is killing me, and applications that aren't willing towait for it to respond Pocket <pocket@columbus.rr.com> - 2023-12-13 20:10 +0100
Re: raid10 is killing me, and applications that aren't willing towait for it to respond Pocket <pocket@columbus.rr.com> - 2023-12-13 19:50 +0100
Re: raid10 is killing me, and applications that aren't willing towait for it to respond Dan Ritter <dsr@randomstring.org> - 2023-12-13 20:10 +0100
Re: raid10 is killing me, and applications that aren't willing towait for it to respond Pocket <pocket@columbus.rr.com> - 2023-12-13 20:20 +0100
Re: raid10 is killing me, and applications that aren't willingtowait for it to respond gene heskett <gheskett@shentel.net> - 2023-12-13 20:30 +0100
Re: raid10 is killing me, and applications that aren't willing to wait for it to respond "Andrew M.A. Cater" <amacater@einval.com> - 2023-12-13 19:30 +0100
Re: raid10 is killing me, and applications that aren't willing towait for it to respond "Andrew M.A. Cater" <amacater@einval.com> - 2023-12-13 23:00 +0100
Re: raid10 is killing me, and applications that aren't willingtowait for it to respond gene heskett <gheskett@shentel.net> - 2023-12-14 01:10 +0100
Re: raid10 is killing me, and applications that aren't willing to wait for it to respond Andy Smith <andy@strugglers.net> - 2023-12-13 22:40 +0100
Re: raid10 is killing me, and applications that aren't willing to wait for it to respond Andy Smith <andy@strugglers.net> - 2023-12-14 00:10 +0100
Re: raid10 is killing me, and applications that aren't willing towait for it to respond gene heskett <gheskett@shentel.net> - 2023-12-14 00:40 +0100
Re: raid10 is killing me, and applications that aren't willing towait for it to respond David Christensen <dpchrist@holgerdanske.com> - 2023-12-14 04:20 +0100
Re: raid10 is killing me, and applications that aren't willing to wait for it to respond <tomas@tuxteam.de> - 2023-12-14 06:50 +0100
Re: raid10 is killing me, and applications that aren't willing to wait for it to respond Nicolas George <george@nsup.org> - 2023-12-14 10:20 +0100
Re: raid10 is killing me, and applications that aren't willing to wait for it to respond <tomas@tuxteam.de> - 2023-12-14 10:40 +0100
Re: raid10 is killing me, and applications that aren't willing towait for it to respond gene heskett <gheskett@shentel.net> - 2023-12-14 13:10 +0100
Re: raid10 is killing me, and applications that aren't willing towait for it to respond gene heskett <gheskett@shentel.net> - 2023-12-14 12:00 +0100
Re: raid10 is killing me, and applications that aren't willing towait for it to respond Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2023-12-14 22:40 +0100
Re: raid10 is killing me, and applications that aren't willing towait for it to respond gene heskett <gheskett@shentel.net> - 2023-12-15 03:40 +0100
Re: raid10 is killing me, and applications that aren't willing towait for it to respond David Christensen <dpchrist@holgerdanske.com> - 2023-12-15 09:10 +0100
Re: raid10 is killing me, and applications that aren't willing towait for it to respond Andy Smith <andy@strugglers.net> - 2023-12-15 13:30 +0100
Re: raid10 is killing me, and applications that aren't willing towait for it to respond Stefan Monnier <monnier@iro.umontreal.ca> - 2023-12-15 16:00 +0100
Re: raid10 is killing me, and applications that aren't willing towaitfor it to respond gene heskett <gheskett@shentel.net> - 2023-12-16 03:30 +0100
Re: raid10 is killing me, and applications that aren't willing towaitfor it to respond David Christensen <dpchrist@holgerdanske.com> - 2023-12-16 05:00 +0100
Re: raid10 is killing me, and applications that aren't willingtowaitfor it to respond gene heskett <gheskett@shentel.net> - 2023-12-16 16:10 +0100
Re: raid10 is killing me, and applications that aren't willingtowaitfor it to respond David Christensen <dpchrist@holgerdanske.com> - 2023-12-16 21:30 +0100
Re: raid10 is killing me, and applications that aren't willing towaitfor it to respond David Christensen <dpchrist@holgerdanske.com> - 2023-12-16 05:10 +0100
Re: raid10 is killing me, and applications that aren't willing towaitfor it to respond Matt <matt@jmgresham.xyz> - 2023-12-16 05:20 +0100
Re: raid10 is killing me, and applications that aren't willing towaitfor it to respond Greg Wooledge <greg@wooledge.org> - 2023-12-16 05:30 +0100
Re: raid10 is killing me, and applications that aren't willing towaitfor it to respond Matt <matt@jmgresham.xyz> - 2023-12-16 05:30 +0100
Re: raid10 is killing me, and applications that aren't willing towaitfor it to respond Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2023-12-16 09:30 +0100
Re: raid10 is killing me, and applications that aren't willing towaitfor it to respond David Christensen <dpchrist@holgerdanske.com> - 2023-12-16 20:20 +0100
Re: raid10 is killing me, and applications that aren't willing towait for it to respond Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2023-12-16 09:50 +0100
csiph-web