Re: [arch-general] Suspicious activity and slowness ...
On Mon, 17 Dec 2018 at 16:04, Peter Nabbefeld wrote: > > since some days, I'm noticing HD is too busy, and my laptop is very slow > in some cases. > > Are there any invisible background threads running? How can I find out > about those? Running top, cpu use should be only about 30%, so it should > wait for tasks to be executed, instead. According to these two I suggest you take a look at the load, as it measures responsiveness more correctly than cpu time, as data transfer usually clogs up the machine the same as computing does. Use htop and turn on the IO_RATE column to find out which process uses your disks. Also, you might need to run as root to see the details of all processes. -- Oliver
Re: [arch-general] JOB | Permanent Database Engineer (the Netherlands or remote)
> Registering just to promote your issue/cause, FOSS-related or not, > treats the community as a resource and is not acceptable; [...] Even more so, considering the only other email sent from this address: https://lists.archlinux.org/pipermail/arch-general/2016-November/042624.html -- Oliver Temlin
Re: [arch-general] Dual boot issue, windows doesn't show up on grub
On 26 July 2017 at 09:39, David C. Rankin wrote: > How are you handling the UTC/localtime issue between Linux/windows? Registry > hack in win? Or, are you running Linux with hwclock set to localtime? If you > are allowing systemd-boot, or grub, or syslinux to choose the OS, what is > setting the hwclock appropriately between differing OS boots? Registry hack and disabling NTP in Windows works fine for me. The bootloader has nothing to do with it, systemd's NTP solution already has hwclock committing built into it. BTW, I'm using UEFI and change via the system boot menu, as it asks for a password, unlike systemd-boot. -- Oliver Temlin
Re: [arch-general] How much people use Arch Linux
A good statistic would be from the downloads on the filesystem/coreutils/pacman packages, but you would need to get all the mirrors to track that. Also, that still measures the number of machines and not the users. -- Oliver Temlin
Re: [arch-general] RAID-0 kernel bug
On Sat, May 23, 2015 at 04:16:59AM -0500, David C. Rankin wrote: > UUgh, dumb question, but... I have not used/configured this "discard", but I > do have 6 Raid0 arrays spinning on my Arch server. Does this corruption > potentially apply to me? Is this "discard" something that would be enabled > by default? I have never heard of it, so that is the only thing to that > concerns me. From the kernel thread, the fix is out on 5/22. What do I do to > test whether I suffered corruption? Hello! Discard is an option to use the built-in deletion function of flash storage drives, so no hard disks are vulnerable. Assuming that your drives are actually 'spinning' in your server, it's safe to assume that you are free of this bug. > -- > David C. Rankin, J.D.,P.E.
Re: [arch-general] Reconverting to Arch
On 25 November 2014 at 23:25, Hunter Jozwiak wrote: > Hi ladies and gentlemen. I am going to reconvert back to Arch. > I have one particular question: do I need to do any extra steps when making > BTRFS filesystems on a fresh install? If your root is on a subvolume, just set it as the default. > And what nasties should I be awar" of whe using BTRFS? Free space measurement is still somewhat off. Use btrfs' df implementation instead of the coreutils one. Also try not ever to fill your disk over 95%, because otherwise nasty things still ensue (although you can now delete files on a full filesystem). -- Oliver Temlin
Re: [arch-general] Cannot install mlpack from AUR
On Wed, Oct 29, 2014 at 9:10 PM, Thorsten Jolitz wrote: > I cannot install the mlpack package from AUR Since AUR is officially unsupported on arch, you are probably either looking for the aur-general list or the package comments at [1]. I'd recommend the comments, since it bothers less people, but beware that usually only the maintainer is subscribed, so it might take a few days to get an answer. [1] https://aur.archlinux.org/packages/mlpack -- Oliver Temlin
Re: [arch-general] Dell latitude and keyboard problem
> Actually, I've noticed this problem on my dell e7440 after updating the bios > to A10. Unfortunately, I've not written the previous version I was using > before (probably A08). > Thanks for Your answear. As I wrote, I start more using Windows last few days and in Windows 7 I installed virtualbox with Lubuntu 14.04. Today when I work on this Lubuntu in VM that issue happend again. In Windows it not happens any time. I have really no idea what could be a reason. > It is also probably not problem with config because some time ago I was checking it on Ubuntu Live and that was also happend :/ Hello! Now this could be an evil and unsupported way, but try downgrading the bios to A09 or even A08 and test that. Also, now that this happens in a VM the issue could be raised to Dell support, as it should be a supported system. -- Oliver Temlin
Re: [arch-general] Btrfs blues - lack of space
> Again, another weird thing is that the btrfs filesystem df /home showed 398 > gigs to space in home before all this, and now it shows 402 gigs. Something > is definitely up. As per my experience, always sync before measuring free space. - -Oliver Temlin
Re: [arch-general] Btrfs blues - lack of space
> Whenever I start my laptop up, /home takes ~17-19 seconds to mount You can always use x-systemd.automount in fstab, which delays the mount to the first access (ie. non-root login), or mask home.mount to be non-blocking (oneshot), so it runs parallel with the login manager and password input. Slow mount times are usually caused by large log trees and fragmented metadata. Try the autodefrag mount option and btrfs fi defrag -clzo -t 2M -r /home (defragment files over 2M in size, recompress with lzo, recursively), btrfs balance start /home (and wait for btrfs-endio-wri to calm down or check with balance status, this takes some time) If those don't help enough, try checking (but not repairing) the device with btrfsck, and, if it's clean, clear the logs with btrfs-zero-image after backing up the metadata with btrfs-image (consult the btrfs mailing list or IRC first, I am not an expert in this). > Running df -h on my system, I get: > /dev/sda5 422G 364G 53G 88%/home Please use btrfs filesystem df (fi df for short), as it will show you both the data and metadata allocation with better reflection on actual free data space. Point is, the allocation on B* trees can only be measured by a full tree traversal (as your du try shows the true data usage, but misses fragmentation), but btrfs usage is even more complicated. Authors suggest that a device never be filled over 75% to avoid metadata fragmentation, but by having larger files this can truly be about 95%. Sorry for the long text, but I belive this helps in better understanding. --Oliver Temlin
Re: [arch-general] fstab and root filesystem
> Thanks a lot, Temlin! About root fsck, I guess it should be run from the > initramfs...? AFAIK, rw-mounted filesystems must not be checked. That's exactly what happens, see the service file: "ConditionPathIsReadWrite=!/" So you proabably have to add the ro option (if that's not the default), because systemd will remount r/w: systemd-fsck-root.service is before local-fs.target which wants systemd-remount-fs.service, but the man page for the latter mentions that it only runs entries that exist under fstab. I suggest you try it without an entry in fstab, both with ro and rw and report your findings to the fstab page on the wiki. -- Oliver Temlin
Re: [arch-general] fstab and root filesystem
Hello! Sure, I've seen some distributions do this, go for it! You can supply everything important in fstab through the kernel command line: device => root; type => rootfstype; options => rootflags Mount point, dump and fsck cannot be supplied, but even fsck is provided by systemd-fsck-root.service. Also mind that you can supply rw or ro for the rootfs to be mounted as such, and that ext2/3/4 can store flags within itself, see -o under tune2fs(8). -- Oliver Temlin On Fri, Aug 29, 2014 at 2:04 PM, Kalrish Bäakjen wrote: > > Hello, > I have been playing with the initramfs, and I noticed that the root > filesystem is mounted in read-write mode in early init. Since, by the time > /etc/fstab is available, the filesystem on which it resides (presumably, > the root filesystem) is already mounted, and mounting it is anyway early > init's task, not real init's (because the real init cannot be found without > the initramfs), there seems to be no point in keeping it listed. I haven't > found anything about this, but commenting out the pertinent line hasn't > broken anything. Is it fine, or are there any reasons for it to be listed > in fstab? > > Regards, > Kalrish
Re: [arch-general] File conflict between cuda and pacparser
>>>> $ sudo pacman --force -S pacparser cuda >>> >>> That was a horrible thing to do, and an even worse thing to recommend here. > > What exactly is horrible? The OP needs the software and the conflict is > just a man page. IMO it's a valid workaround, exactly what the --force > option should be used. It's a policy to keep users from learning bad things. You should never suggest --force or a package from AUR unless you attach a big fat warning, otherwise it would mean to encourage them to do it in other (seemingly indifferent) cases, eg. updating filesystem with --force can mess things up pretty badly. -- Temlin Olivér
Re: [arch-general] 3.15 kernel breaking X ?
On Mon, Jul 7, 2014 at 10:21 AM, Daniel Petre wrote: > Apologies but i do not know how to reinstall the 3.14 kernel, linux is 3.15 and linux-lts is 3.10.. > Can i get from some repo the 3.14 package? > Thanks. There's no repo, but you can get old versions from the Arch Rollback Machine (obviously expect no support): http://seblu.net/a/arm/packages/l/linux/ Then just install with pacman -U -- Oliver Temlin
Re: [arch-general] Docked Lenovo T540p Not Recognizing Dual Monitors
It looks like the VGA display is not even recignised as existing. Try it with only the VGA plugged in, and see whether it gets recognized as such. The Lenovo page [1] writes about one model that only some video outputs are separate (some are exclusive). If it is so, then try chatting up tech support (mentioned page pops up such option after some time) and ask which ones are separate. [1] http://shop.lenovo.com/us/en/itemdetails/40A20090US/460/6D501EE899104FF9A362D739642CFC27 -- Oliver Temlin On Fri, Jun 27, 2014 at 5:51 PM, Jude Lucien wrote: > But the burning question is how can I get my VGA monitor to be recognised?
Re: [arch-general] 'grub_term_highlight_color' not found
Since when is there an m switch to rm? For me, it is "rm: invalid option -- 'm'". Yeah, updating arch without doing so for months might be breaking things, but I belive this problem was caused by you creating malformed config files (at least to the installed version). Also, you might try making a systemctl service which sets the efi bootnext variable on start (I do so, because Dell doesn't let you put uefi before legacy in the bootorder) -- Oliver Temlin On Thu, Jun 5, 2014 at 10:53 AM, Dimitris Zervas wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > So, yesterday night, I decided to update my system. I had 4-5 hours to deal > with all the nuclear blast that an update of 3 months would cause (the good > old arch we all love... I don't know which is worse, rm -rm / or pacman > -Syu?). > After 10-20 everything was updated and decided to restart. > Also, I wanted to change the boot order of my UEFI and boot arch by default > instead of win (finals are over). > I made the change and saved. The scree was blank for ~10s and I decided to > hard reboot. BOOM. > > The uefi entry was lost. Also, if I launched grub2 as a uefi shell (which I > have for times like that) I got "error: symbol 'grub_term_highlight_color' > not found" and grub gives me a rescue terminal. > > The first problem (uefi entry) is very painful. I have an Asus P9X79 Deluxe. > It does NOT support v2 uefi shell (so, no bcfg) and no matter how hard I try > to add an entry with efibootmgr, nothing happens (via SysResCD, uefi mode > boot with modprobe efivars) > > The second problem (grub pukes) I have no clue what's going on. I just > updated, even tried grub-mkconfig via chroot and nothing changed. I found 2 > threads on arch forums which where not helpful at all. > > Any help appreciated :) > -BEGIN PGP SIGNATURE- > Version: APG v1.1.1 > > iQJCBAEBCgAsBQJTkC/tJRxEaW1pdHJpcyBaZXJ2YXMgPGR6ZXJ2YXNAZHplcnZh > cy5ncj4ACgkQ+77hPkfJypZSeA/8DcxVPg+WWDva/E2hfjX5e1OFTMJbxcweWmBG > hDoNDShtm1sDfJ057fmidYqozud6ytNpug9qu+ixIBCRqmOfETjcSogNkr09Dfs5 > zr0Opm15AQDlCmXcnfFWY8cPeEl8I+LqdoJM5RMM3Z6an6QmvVETdxVQ6wxouVgL > AvHd7Lk/aNAYLN6uI8JFBOX0H9CzjCB/sviYmOwmVkFZLlVOKkJiYpWHL8p4pUCp > Wf+2CUu42wvvvaSdrdiddc1WVHcCknr1HEYK4juiJCCgCUldUwRZGXJiS2j/0ZH/ > L+VoufUMqlc+NWjV67PtwhmtVl9jvrcymAA2UOAnrWAvZZjynMyFIspdDiBffWP+ > Cw+01oubUDPW2NI/9HiLm2u0QohemlYHPoFoM1a5nhsXG0pC/6qqzT0DEy3K2pl2 > a+FkNum8KVl6vmtS3JXvXeH1HRKJ6aIK7qSinATKjK/Ust7saC0TsHZieWSNqZ+v > 7OFOd5IYkMJyKxBuwvrpcplJmfbYuSnjRwP+OYf7nsZXNKKhPjvYi5mO1hw1fHOK > Bd9GMxOjOaPrQHXSl8iJ3BTUXAXcBGZ/gbXyqyx6mieWwOGuhix/IwkoVsJU2j3i > 6/TsGhykK5STdMG6augYugcPkkgdjqCteJx+LHP0By45bY6e7S9WOnmpJdzubWPJ > nKoE3JY= > =uxTT > -END PGP SIGNATURE- >
Re: [arch-general] Is ATI more... "compatible"?
> It will just hand it to the VM (windows) via VGA passthrough (either Xen or > KVM will be used). > Is that impossible to do with my NVidia? > If it is possible, is it easier with the ATi equivalent? It was already answered. You would be handing the PCI device over to windows (since you have another dedicated to linux), so the make does not matter in this case. If you can accomplish that with your current card, than chances are you can do it with any other. What matters is the kernel (and probably motherboard) support for the passing of raw PCI devices, so a better question would be whether to use Xen or KVM and on what motherboard. - -Oliver Temlin
Re: [arch-general] creating an archlinux usb key with persistence
>> My setup right now is this: >> >> 32GB usb3 drive >> |-sda1 (4G) - fat32 >> |-sda1 (256M) - ext4 /boot >> |-sda2 (rest of drive) - luks - btrfs - subvolumes for root and home > Sounds likea good setup. > > What tool are you using for partitioning? I don't remember luks/btrfs as an option in fdisk, admittedly I am coming from a debian perspective just switching to arch to try it out. > Sounds likea good setup. Just make it whatever you want, it doesn't really matter in linux, where identification goes by magic numbers, not such things as this and extensions. You can easily follow the wiki with setting up dm-crypt/LUKS and btrfs subvolumes. Also, please append mesaages to the bottom, as to keep messages in a chronological order. --Oliver Temlin
Re: [arch-general] creating an archlinux usb key with persistence
On Mar 13, 2014 2:56 PM, "Mark Lee" wrote: > > Salutations, > > Do you know how stable F2FS is (the Phoronix benchmarks don't tell us > anything about data permanence)? > > Regards, > Mark A quick search for 'samsung phone data loss' comes up only with undeleting methods and a virus. Since Samsung uses F2FS for some time on their phones, I'd expect data permanence will not be much of a problem. But after using btrfs on an ssd for a year and some, I'd suggest that also, but take care not to fill the disk up too much, as btrfs ondemand optimization will slow down your machine with low free space. - -Oliver Temlin
Re: [arch-general] Cannot recover pacman upgrade fails problem
On Mar 10, 2014 4:18 PM, "Cao, Renzhi (MU-Student)" wrote: > > Hi, > I use this system for almost one year, and don't update the system. I have tried mount /dev/sda3 as the root directory. And I try one thing before chroot: > #mkdir /mnt/bin > #cp /bin/* /mnt/bin > #arch-chroot /mnt > > Now I can go to the chroot jail. And surprised to me, I run the following command, and I don't see any fails: > #mv /bin/* /usr/bin/ > #rmdir /bin > #pacman -Syu mkinitcpio systemd linux > . > > Now I am going to reboot my system, hopefully, it's going to work. Thanks. > > > > Renzhi Cao > > Email : rc...@mail.missouri.edu Hello, If that should work, then try upgrading filesystem asap, and expect many '/usr/bin/file already exists in filesystem' errors on subsequent updates. Make sure, that they are unowned according to pacman (pacman -Qo /path/to/file), and remove them before continuing. Also make sure to never reboot between removing the files and upgrading these packages. --Oliver Temlin
Re: [arch-general] Cannot recover pacman upgrade fails problem
On Mar 10, 2014 4:51 AM, "Cao, Renzhi (MU-Student)" wrote: > > Hi, all: > > I really have no idea for the pacman upgrading fails issue, so I summarize the problem I meet, and the things I try, if any one can give me suggestions of what I miss something or I do something wrong, I really appreciate, if not, I hope this summation can benefit some other people who meets the same problem. > > > The initial problem: > > After using pacman -Syu --ignore filesystem to upgrade my arch linux, and reboot, get the following message: > > ERROR: device '/dev/disk/by-uuid/3f51b ...' not found. Skipping fsck. > > ERROR: Unable to find root device '/dev/disk/by-uuid/3f51b ...'. You are being dropped to a recovery shell. > > You are being dropped to a recovery shell > > Type "exit" to try and continue booting > > sh: cant access tty; job control turned off. > > [ramfs /]# _ > > > > The solution may be used to solve this problem : https://wiki.archlinux.org/index.php/pacman#Q:_After_updating_my_system.2C_I_get_a_.22unable_to_find_root_device.22_error_after_rebooting_and_my_system_will_no_longer_boot > > > I first try the first method, not work, and then try the second method: > > The following is the command I run and the output after I use a live CD for my system: (People have similar problem can consider it) > > #fdisk -l > > /Dev/sda : 2000.4 GB. > > Device boot|start|end|blocks|id|systems > > /dev/sda1 … Linux swap/solaris > > /dev/sda2 … Linux > > /dev/sda3 … Linux > > Disk /dev/mapper/arch_root-image > Units ... > > Sectorsize ... > > > #mount /dev/mapper/arch_root-image /mnt > > #mount /dev/sda3 /mnt/home > > #mount /dev/sda2 /mnt/boot > #arch-chroot /mnt > > #pacman-key --init > #pacman-key --populate archlinux(This command is needed for the signiture, it takes me a while to figure out this). > #pacman -Syu mkinitcpio systemd linux > > (133/133) checking for file conflicts [##] 100% > error: failed to commit transaction (conflicting files) > filesystem: /bin exists in filesystem > filesystem: /sbin exists in filesystem > filesystem: /usr/sbin exists in filesystem > Errors occurred, no packages were upgraded. > (I Check this website for the solution: https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention ) > #pacman -Qqo /bin /sbin /usr/sbin | pacman -Qm – (you may get different output, the following is mine) > > sysvinit-tool 2.88-9 > > lilo 23.2-3 > > grub-common 2.00-1 > > sysvinit-tool 2.88-9 > > lilo 23.2-3 > > #pacman -R lilo > #pacman -Syu --ignore filesystem,bash > #pacman -S grub > #pacman -S sysvinit-tools > #pacman -S systemd > #pacman -S bash > #pacman -Su > #pacman -Syu mkinitcpio systemd linux (now for me, this command can run successfully) > #exit, and umount, reboot > > After rebooting, I get the following error: > /dev/sda3: clean ... > > ERROR: root device mounted successfully, but /sbin/init does not exist. > > Bailing out, you are on your own. Good luck. > > Sh: cannot access tty: job control turned off. > > [rootfs/]# _ > > > (I check this website for the solution:1. Add "init=/bin/systemd" to the kernel line, based on https://bbs.archlinux.org/viewtopic.php?id=146388 > > 2. Add "init=/usr/lib/systemd/systemd" to the kernel line, based on https://bbs.archlinux.org/viewtopic.php?id=166423) > > None of them work for me. > > > Here is the command I run in rootfs : > > #ls > > bin,buildconfig,config,dev,etc,hooks,init,init_functions,lib,lib_64,new_root,proc,run,root,sys,tmp,usr. > > I check the folder new_root, it is my system's root folder before it crashes. I don't know how this new folder comes, I am guessing I do something wrong for arch-chroot? > > > I checked : > > #ls -l /sbin/init > > 7 Mar, /sbin/init -> busybox ( the same output for ls -l /bin/init) > > #ls -l /bin/systemd > > No such file > > #ls -l /usr/lib/systemd/systemd > > No such file > > It seems I miss something, and I remember I do reinstall the grub and sysvinit-tools before I quit arch-chroot. > > > Welcome to ask me questions for some details if you have the same problem, and welcome to give me suggestions. ? > > Thank you all! > > > > Renzhi Cao > > Email : rc...@mail.missouri.edu< https://bluprd0112.outlook.com/owa/redir.aspx?C=HgdIKZwfkkG-ZqHZQdR5l5Qjeol9gdAIEexz2Okb9KSvfYJfxGlJ7wHelHyOveteZCNx50ztf78.&URL=mailto%3arcrg4%40mail.missouri.edu > > Everything has moved to /usr/bin, try init=/usr/bin/systemd If you have removed the conflicting packages, then update filesystem, msking the symlinks, so that /bin/* will not fail anymore. Also, update more often and subscribe to arch-announce (or watch the mainpage news), or consider moving to a non rolling-release distro, as Arch tends to suffer from rare updates. --Oliver Temlin
Re: [arch-general] doubts about rolling release
Hello, and welcome to the arch side! The transitions are made so that if you update often enough and do as the postinstall scripts and main page tell you to, then the transition goes easily. Both the systemd and moving to /usr/bin were done almost automatically (systemd had initscripts support for about a year, now still there as an option), the other also did have a few-minutes solution to most problems. However, there are some packages for which support is weak, usually for other major distributions not having them adopted yet, eg. bluez 5 was unusable for about half a year, now Apache 2.4 seems to be the same way, but these are supported by keeping the old versions in a separate, but compatible package (eg. bluez4, gtk2). --Oliver Temlin On Mar 7, 2014 7:09 PM, "Ary Kleinerman" wrote: > Hi, > I'm a new Archer and I'm planning to install arch linux in a production > server environment, but I have doubts because Arch is a rolling release. My > question is: what does it happen when there are big changes? e.g. changes > in the filesystem or when Arch has started using systemd. > Regards, > Ary > > -- > *Ing. Ary Kleinerman* > Building Networks S.A. > Córdoba, Argentina > +54 351 5544150 >
Re: [arch-general] Xorg doesn't start
> Subsystem: Samsung Electronics Co Ltd Radeon HD 6750M Is it a laptop? That M suggests it is. Laptops also have an Intel card, which is connected to the display, while the ati/nvidia one is not. Try with xf86-video-intel, and check the wiki for discrete graphics card support. --Temlin Olivér
Re: [arch-general] Thank you
On Tue, Jan 7, 2014 at 9:15 AM, Martti Kühne wrote: > > Thinking out loudly, arch is a lot of fun. Except for my occasional > wrestles with systemd and its sort of layer cake it's awesome. If you > need your graphics driver modprobed by the time X should launch you > can put it into mkinitcpio.conf. And if you put stuff into > mkinitcpio.conf, remember to argh build the image. /me swearing like a > trooper. > For crying out loud, there went an hour of puzzlement. > > cheers! > mar77i mkinitcpio.conf puts stuff into your initrd, you should probably use modules-load.d/graphics.conf, see modules-load.d(5) and [1]. But as I am posting in this thread, I too would like to say thanks for making this simplie yet so powerful distribution. [1] https://wiki.archlinux.org/index.php/Modprobe.d#Using_files_in_.2Fetc.2Fmodprobe.d.2F -- Temlin Olivér
[arch-general] Package management
t the Arch Way: outdated packages go to the repos and it would complicate the system even more, using the libpng example, the AUR contains three additional packages, making the count 5. Putting these in the official repos would encourage developers to keep using old libraries for their projects and force the user to (in your alternatives-manager-style version) to change library symlinks repeatedly. So the arch solution to your problem is to notify bar1 upstream, and if they don't make a solution (usually because debian/ubuntu not having the new library versions yet), then make a custom patch, or if there are only a few users, and/or a dead upstream, drop the package, which has a (high) chance to resurrect in the AUR. Just bringing up an example search for gnome at the forums around 2011-04 and a few months forth. Dozens of people wanted back the old Gnome 2 (including myself), whined (not me), but to no avail. All the answers were all no. Arch is not going to support (or even ship) packages that are out-of-date. The current solution is to use the since-developed MATE and Cinnamon derivatives. But I'm just a user, and these are my thoughts, not completely matching the arch developers' ones. -- Temlin Olivér
[arch-general] Notebook freeze and slow when copy big files to external usb
Try disabling USB emulation on your motherboard. I had the same problem and this helped a lot, even if it is not a complete solution. --Temlin Olivér On Dec 4, 2013 5:47 PM, "Maykel Franco" wrote: > Hi, I when I make a copy of a large file to a 2GB or 8GB usb 3.0 > external hard drive, I notice that arch remains slow, frozen ... He > struggles to open windows are minimized. I have the kernel: > > 3.12.2-1-ARCH > > Update the whole system to the last. Can you think because it can be? > > I also went from the 3.11 kernel > > However, debian, ubuntu, opensuse me not pass this ... > > It's happened to someone else? > > Thanks for everything. >
[arch-general] fsck.f2fs and systemd
On Oct 31, 2013 10:29 AM, "Simon Perry" wrote: > - Is there any way to override how systemd does its fsck? I've tried > poking around and overriding systemd-fsck-root.service and > systemd-fsck@.service to no avail. Any advice on this? Fsck'ing can be disabled in the fstab file, and you can try to write a custom systemd module to do it. > - Should systemd always expect an fsck tool to accept that the "-a" > arg works, therefore an issue for f2fs-tools upstream, or should > systemd be aware of this (therefore an upstream issue for systemd). It is a standard that init and systemd pass an -a to the fsck denoting that there could be no user interaction. This is why btrfs-tools ships only "btrfsck" which is not recognized as an fsck.fstype command by the initscripts. So at least ask the packagers to move the command to f2fsck as to not confuse init (or systemd in Arch). --Temlin Olivér
