Re: [gentoo-user] experiences with zfsonlinux?
Yeah, I use ZoL for my home server (mostly pictures, videos, and mp3s) and it works just fine. SSD for the / and /boot, and then ZFS for all the important data in a mirrored pool. Highly recommended. (Just updated to 3.7.1 kernel and 0.6.0-rc13 ZoL, with no issues, in case you were worried about usage with "current" pieces.) ScottE On Fri, Dec 28, 2012 at 12:29 PM, Stefan G. Weichinger wrote: > Am 2012-12-28 18:52, schrieb Volker Armin Hemmann: > > Hi, > > > > so in the Good/better/best filesystem for large, static video > > library? thread zfs was mentioned, since I just ordered 3 new hdd to > > replace the current 5 in my box (3 in raid5, 2 in raid1 > > configuration), I asked myself: instead of raid5+xfs or ext4 or > > whatever else that might be a sane solution, why not try zfs? > > Sure, go ahead :-) > > > But - there aren't so many first hand accounts on people using the > > spl+zfs kernel modules on linux. > > > > Anybody done it? Any caveats? > > I used it in a former server in my basement, right now the zfs-pool is > out of order simply because I have no SATA-ports available right now > (broken mainboard etc) > > It is the equivalent of a RAID1 mirror, 2 disks in a tank. > > As you may have researched already it is not necessary to partition the > disks, back then it was recommended to create the pool/mirror by using > the /dev/disk/by-id/ device-notation. > > That pool worked very well for me and even caught SATA-related errors > with the occasional scrub-run here and then. > > I even was able to migrate that mirror from zfs-fuse to zfs-on-linux > without any problems. > > As soon as I have a box with enough hdd-bays again I will re-import that > pool for sure. > > Good luck, Stefan > >
Re: [gentoo-user] experiences with zfsonlinux?
I think it's a bug, but "zfs mount -a" works around it quickly. On Sun, Dec 30, 2012 at 7:42 PM, Volker Armin Hemmann < volkerar...@googlemail.com> wrote: > one thing that baffled me was when I set the mountpoint for zfstank/var - > and > it was gone. ;) >
[gentoo-user] Failure of zfs-kmod with 3.13.* kernel
When trying to build zfs-kmod against a a 3.13.[0|1|2] kernel, spl works fine, but zfs fails. It looks like the issue is that the configure script isn't doing quite the right check for bdi_setup_and_register, so HAVE_BDI_SETUP_AND_REGISTER doesn't get defined, and then there's a mismatch in the definitions between zfs and the kernel source. The offending bit in the configure log looks to be: configure:17996: checking whether bdi_setup_and_register() is available configure:18024: cp conftest.c build && make modules -C /usr/src/linux EXTRA_CFLAGS=-Werror M=/var/tmp/portage/sys-fs/zfs-kmod-0.6.2-r3/work/zfs-zfs-0.6.2/build /var/tmp/portage/sys-fs/zfs-kmod-0.6.2-r3/work/zfs-zfs-0.6.2/build/conftest.c: In function 'main': /var/tmp/portage/sys-fs/zfs-kmod-0.6.2-r3/work/zfs-zfs-0.6.2/build/conftest.c:91:25: error: ignoring return value of 'bdi_setup_and_register', declared with attribute warn_unused_result [-Werror=unused-result] bdi_setup_and_register(NULL, NULL, 0); ^ Anyone else seeing this?
Re: [gentoo-user] Failure of zfs-kmod with 3.13.* kernel
Ah, I missed that bug report. Thanks for the pointer (and the workaround). On Sat, Feb 8, 2014 at 11:50 AM, Neil Bothwick wrote: > On Sat, 8 Feb 2014 10:07:31 -0800, Scott Ellis wrote: > > > When trying to build zfs-kmod against a a 3.13.[0|1|2] kernel, spl works > > fine, but zfs fails. It looks like the issue is that the configure > > script isn't doing quite the right check for bdi_setup_and_register, so > > HAVE_BDI_SETUP_AND_REGISTER doesn't get defined, and then there's a > > mismatch in the definitions between zfs and the kernel source. The > > offending bit in the configure log looks to be: > > Bug report with hacky workaround > > https://bugs.gentoo.org/show_bug.cgi?id=499672 > > Works for me. > > > -- > Neil Bothwick > > Profanity, The Language of Computer Professionals. >
Re: [gentoo-user] Nvidia and Radeon video cards in the same box.
I was never able to get the ATI supplied drivers (fglrx) to work with any other Xorg server drivers. My specific use case was to have X displaying on 8x R9-290X cards and an AST2400 at the same time. Regardless of what I did, the ATI driver would segfault on startup if the AST module was configured. :-( (It looked like something in how the fglrx driver was exposing OpenGL resources, but I didn't dig terribly deep.) My point is..."odd" behavior with ATI and "something else" at the same time isn't confined to you. :-) ScottE On Thu, Feb 5, 2015 at 3:22 PM, Linux wrote: > > > On 2/5/2015 2:46 PM, Mickaël Bucas wrote: > >> 2015-02-05 17:32 GMT+01:00 Linux : >> ... >> >>> [ 1066.959] (II) [KMS] drm report modesetting isn't supported. >>> >> ... >> >>> [ 1066.961] (EE) Screen 0 deleted because of no matching config section. >>> [ 1066.961] (II) UnloadModule: "radeon" >>> >> ... >> >>> [ 1067.703] (II) AIGLX: Screen 0 is not DRI2 capable >>> [ 1067.703] (EE) AIGLX: reverting to software rendering >>> [ 1067.732] (EE) AIGLX error: dlopen of /usr/lib64/dri/swrast_dri.so >>> failed >>> (/usr/lib64/dri/swrast_dri.so: undefined symbol: _glapi_tls_Dispatch) >>> [ 1067.732] (EE) GLX: could not load software renderer >>> >> >> It seems your kernel doesn't support DRI, nor modesetting. >> I would suggest checking your kernel configuration for the options >> needed for radeon driver. >> >> I don't remember how I did but there is the Gentoo Wiki : >> http://wiki.gentoo.org/wiki/Radeon >> >> Mickaël Bucas >> >> > Yes... Thank you. > > However I followed the info at that link best I could, some of the kernel > options were not the same, and now I get nothing but black screens and a > locked up computer. > > Xorg.0.log below > - > [67.594] > X.Org X Server 1.16.3 > Release Date: 2014-12-20 > [67.600] X Protocol Version 11, Revision 0 > [67.602] Build Operating System: Linux 3.18.1-gentoo x86_64 Gentoo > [67.604] Current Operating System: Linux localhost 3.18.5-gentoo #3 > SMP PREEMPT Thu Feb 5 15:56:25 MST 2015 x86_64 > [67.604] Kernel command line: root=/dev/sdb5 softlevel=console > append="acpi_enforce_resources=lax" > [67.608] Build Date: 12 January 2015 09:22:12AM > [67.610] > [67.612] Current version of pixman: 0.32.6 > [67.616]Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > [67.616] Markers: (--) probed, (**) from config file, (==) default > setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > [67.624] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Feb 5 > 16:04:09 2015 > [67.653] (==) Using config file: "/etc/X11/xorg.conf" > [67.656] (==) Using config directory: "/etc/X11/xorg.conf.d" > [67.658] (==) Using system config directory > "/usr/share/X11/xorg.conf.d" > [67.682] (==) ServerLayout "Layout0" > [67.682] (**) |-->Screen "Screen0" (0) > [67.682] (**) | |-->Monitor "Monitor0" > [67.684] (**) | |-->Device "Device0" > [67.684] (**) |-->Screen "Screen1" (1) > [67.684] (**) | |-->Monitor "Monitor1" > [67.684] (**) | |-->Device "Device1" > [67.684] (**) |-->Input Device "Keyboard0" > [67.684] (**) |-->Input Device "Mouse0" > [67.684] (**) Option "Xinerama" "1" > [67.684] (==) Automatically adding devices > [67.684] (==) Automatically enabling devices > [67.684] (==) Automatically adding GPU devices > [67.684] (**) Xinerama: enabled > [67.712] (WW) The directory "/usr/share/fonts/TTF/" does not exist. > [67.712]Entry deleted from font path. > [67.712] (WW) The directory "/usr/share/fonts/OTF/" does not exist. > [67.712]Entry deleted from font path. > [67.712] (WW) The directory "/usr/share/fonts/Type1/" does not exist. > [67.712]Entry deleted from font path. > [67.720] (WW) `fonts.dir' not found (or not valid) in > "/usr/share/fonts/75dpi/". > [67.720]Entry deleted from font path. > [67.720](Run 'mkfontdir' on "/usr/share/fonts/75dpi/"). > [67.720] (==) FontPath set to: > /usr/share/fonts/misc/, > /usr/share/fonts/100dpi/ > [67.720] (==) ModulePath set to "/usr/lib64/xorg/modules" > [67.720] (**) Extension "Composite" is disabled > [67.720] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' > or 'vmmouse' will be disabled. > [67.720] (WW) Disabling Keyboard0 > [67.720] (WW) Disabling Mouse0 > [67.720] (II) Loader magic: 0x806c80 > [67.720] (II) Module ABI versions: > [67.720]X.Org ANSI C Emulation: 0.4 > [67.720]X.Org Video Driver: 18.0 > [67.720]X.Org XInput driver : 21.0 > [67.720]X.Org Server Extension : 8.0 > [67.721] (II) xfree86: Adding drm device (/dev/dri/card0) > [67.721] (II) xfree86: Adding drm device (/dev/dri/card1) > [67.723] (--)
Re: [gentoo-user] SATA drive controller and Linux driver.
Yes, I have that card (well, the 2 internal/2 external port version). Works fine with the AHCI driver on x86_64. No quirks needed, supports FIS, etc. ScottE On Fri, Nov 30, 2018 at 5:50 PM Michael Orlitzky wrote: > On 11/30/18 8:15 PM, Dale wrote: > > > > Does anyone have a card and know for sure that this works and is > > stable? Also, any clues on what driver it takes? > > > > Probably the standard "ahci" driver. > > >
Re: [gentoo-user] SATA drive controller and Linux driver.
I haven't done hot-plug with it, so cannot vouch for that working or not. I use one of the ESATA ports to go to a 4x external drive enclosure (so using FIS), with spinning disks that are solely for backups (zfs send/receive of snapshots), and two of the internal ports for SSDs in a zpool. ScottE On Mon, Dec 3, 2018 at 7:00 PM Dale wrote: > Hi, > > I found the manufacturer website. It says this card supports Hot Plug and > Hot Swap. Have you ever did this? If so, any problems? I don't know why > but outside of USB, that sort of thing makes me nervous. I'm old school I > guess. Plugging things into a computer was always done when the puter was > off. > > Just curious. Oh, I did order a card. Now to figure out the situation on > a hard drive. :/ > > Dale > > :-) :-) > > Scott Ellis wrote: > > Yes, I have that card (well, the 2 internal/2 external port version). > Works fine with the AHCI driver on x86_64. No quirks needed, supports FIS, > etc. > >ScottE > > On Fri, Nov 30, 2018 at 5:50 PM Michael Orlitzky wrote: > >> On 11/30/18 8:15 PM, Dale wrote: >> > >> > Does anyone have a card and know for sure that this works and is >> > stable? Also, any clues on what driver it takes? >> > >> >> Probably the standard "ahci" driver. >> >> >> >
Re: [gentoo-user] Nvidia driver plus kernel info questions
On Sat, May 2, 2020 at 10:33 AM wrote: > > Unfortunatelu "something" is broken, when using the portage version > of the driver. So I removed that driver and installed the same > version as offered by nvidia directlu and that worked. > There's a lot missing in the portage version of the driver - it doesn't even (at least last I checked) install nvidia-ml.so unless you're using X. I suspect your weren't getting libnvoptix installed from portage, which was meaning OptiX won't work. I don't really care for the `.run` version of the drivers, and prefer to keep everything as an ebuild. I have my hacked up ebuild at https://github.com/ScottESanDiego/scotterepo/tree/master/x11-drivers/nvidia-drivers if you wanted to just steal that (it's largely just the original ebuild, but installing extra "stuff" so that nvidia-smi works headless, nvidia-docker works, etc. ScottE
Re: [gentoo-user] Re: Gentoo as NAS
I use Plex via Docker and it works great. Super simple to setup a docker-compose file to bring it up (or even a simple script to 'docker run...'). Data stored on a zpool made up of a pair of 3-drive vdevs. More complex than random FreeNAS/Unraid/Whatever setup, but if you're comfortable enough to use Gentoo, I don't think figuring out ZFS and Docker is much of a stretch. On Thu, Feb 4, 2021 at 5:07 PM Grant Edwards wrote: > On 2021-02-05, Grant Edwards wrote: > > On 2021-02-05, Michael Jones wrote: > > > >> Use the plex overlay. > >> > >> It's updated regularly. Faster than the official gentoo repo was. > > > > This one? > > > > https://github.com/comio/plex-overlay/ > > > > The plex-server ebuild appears to require systemd, but it isn't listed > > as a dependency. Am I missing something? > > Apparently so. The presence of the command systemd_newunit in the .ebuild > doesn't mean that systemd is required. > > >
