XFS Root Filesystem on LVM Stripe - Corruption

I want to create a LVM Stripe across two SATA drives. The problem I keep running into is, on boot, arch reports that a fsck needs to be run on the root filesystem, so it mounts it read only and allows me to type in the root password to get shell access. This all happens after I do the initial arch install, reboot, log in normally, do a pacman -Syu, reboot.
Here's what I have and what I did...
I have two 320G SATA Drives plugged into my system board (an ABIT AN-M2HD). My Bios is set to "AHCI Linux" for the SATA mode.
Boot the latest Arch CD install at command prompt:
cfdisk /dev/sda
create 125M Partition (for /boot) /dev/sda1
create 319G Partition /dev/sda2
cfdisk /dev/sdb
create 320G Partition /dev/sdb1
lvm pvcreate /dev/sda2 /dev/sdb1
lvm vgcreate lvmgrp0 /dev/sda2 /dev/sdb1
lvm lvcreate -i2 -I4 -L1G -nswap lvmgrp0
lvm lvcreate -i2 -I4 -L594G -nroot lvmgrp0
/arch/setup (I'm going to abbreviate this)
Hard Drive Setup (chose option 3)
Set swap to swap LV
Set root to root LV (xfs)
Set /dev/sda1 to /boot (ext3)
/etc/rc.conf USE LVM="YES"
Kerel Params = Boot from LVM Support? I answer Yes
Grub Looks Good.
Everything seemingly installs fine, I can reboot and arch comes right up. But after I do pacman -Syu everything goes to pot.
I suspect I have something wrong in alignment between the LVM stripe and XFS, but dont know..
alternately, should I set my LVM Stripe Size to a value larger than 4? I thought since on i686 max XFS block size is 4096 (4K) then they should match. Any thoughts on this?
help! ;-)
Ether..

I just wanted to add an update. It wasn't a LVM issue, it was a XFS issue.
I went to Arch 64 bit for a while and everything (above) worked just fine.. The usability and Lib32 issues with 64 bit lost it's luster and last weekend I went back to 32 bit Arch.
In going back to 32 bit I followed my procedure above for partitioning just as I had with the 64 bit version and after rebooting from the install and updating packman, the same thing occurred, the file system would start to corrupt, pacman would complain that libraries were truncated and so forth. After reboot, the /root partition would not mount read/write because it was not clean...
I reinstalled Arch 32 bit 6 times on Saturday trying various things in a scientific way and came to this conclusion:
__and I have no idea why__, but when I use the XFS file system on an install with Arch 32 bit, it hoses up. "Your Crazy" you might say, but trust me I've tried it different ways more than a dozen times. (I'm no n00b either, I've been an RHCE since 2003 and a daily Linux user since 1999.) Seems crazy, but XFS was a constant in all of my testing. The only thing I can figure is that it's my hardware and that's just a guess. 64 bit worked without a hitch with XFS. I even got desperate and installed / on a lone 60 gig partition (/dev/sda1) completely deleting all LVMs and it still corrupted with XFS and 32 bit
The Solution?
I used JFS. I have created the LVM Stripe as I have described above and it works great. No issues.
Weird..
For the sake of knowledge I have a:
AMD 5000+ Black Edition CPU
Abit AN-M2HD Motherboard
2 Gig Dual Channel RAM (2x1Gb)
2 320 Gig SATA Drive
1 SATA DVD Writer
-Ether..
Last edited by EtherNut (2008-01-29 14:54:01)

Similar Messages

Increase root filesystem size with VxVM

Hi All,
Can i increase the root fileystem size in solaris 10 after encapsulating the root disk into VxVM.
Thanks
---MGP---

I wouldn't try it.
If you have a mirror, I'd drop the mirror, copy everything over to the mirror disk (in normal, contiguous slices), then redo the VxVM encapsulation.
Root filesystem cannot be discontiguous, no concats, stripes, raid5s, only mirror. So growing is difficult unless the space is already past the end.
Easier to copy to another disk, reset the bits (/etc/system, /etc/vfstab), then boot from it.
Darren

LVM drives not showing on sucessfull boot (/root is on lvm)

I really don't know how this is possible but I have my system booting. It works fine till it makes it to checking filesystem then it complains that it can't find device /dev/mapper/array-root. That is the location of the root filesystem the one it's booting. It then drops me to a maintenance shell. I went into /etc/fstab and changed the pass on my 2 lvm mounts to 0 and I now boot into a working system.
When I check mount it shows that root is /dev/mapper/array-root
but when i go to /dev/mapper/ it does not exist.
I have uselvm="yes" in /etc/rc.conf
I really don't know whats going on here it seems like it's not detecting the lvm volumes even though it's booting off one.
Any help would be really great.

Have you added 'lvm2' to your hooks array in mkinitcpio.conf?

CentOS based linux VM running on Hyper-v : Checking root filesystem fails when kernel switches having old PV(para virtualised driver based on 2.6.32 linux kernel) to new PV(which is equivalent to linux integration component 3.4)

hi all,
I am running a CentOS base VM on top of Hyper-V server. I upgraded PV drivers of Hyper-V in linux kernel 2.6.32 in order to support
Windows Server 2012, then i am hitting below issue on Windows Server 2008 when kernel switches from old PV(which is 2.6.32 based) to new PV(which is equivalent to linux integration component 3.4).i
am hitting following filesystem check error messages :
Setting hostname hostname:
Checking root filesystem
fsck.ext3/dev/hda2:
The superblock could not be read or does not describe correct ext2 filesystem. If the device is valid and it really contains an ext2
filesystem(and not swap or ufs or something else),then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
: No such file or directory while trying to open /dev/hda2
*** An error occurred during the filesystem check.
*** Dropping you to a shell; the system will reboot
*** When you leave the shell.
Also, when I go to the repair filesystem mode. I found out the strange behaviour when i ran those command :
(Repair filesytem) 1 # mount
/dev/hda2 on / type ext3 (rw)
proc on /proc type proc (rw)
(Repair filesystem) 1# cat /etc/mtab
/dev/hda2 /ext3 rw 0 0
proc /proc proc rw 0 0
(Repair filesystem) 1# df
Filesystem 1K-blocks used Available Use% Mountedon
/dev/hda2 4%
I think for all above command there should be /dev/sda2 instead of /dev/hda2.
Also my fstab , and fdisk -l looks like ok for me.
(Repair filesystem) 1# cat /etc/fstab
LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
LABEL=swap-xvda3 swap swap defults 0 0
(Repair filesystem) 1# fdisk -l
Device Boot Start End Block Id System
/dev/sda1 * 1 49 98535 83 Linux
Partition 1 does not end with cylinder boundary.
/dev/sda2 49 19197 39062500 83 Linux
Partition 2 does not end with cylinder boundary.
/dev/sda3 ......
Partition 3 does not ......
/dev/sda4 ......
Partition 4 does not end ....
(Repair filesystem) 1# e2label /dev/sda1
/boot
(Repair filesystem) 1# e2label /dev/sda2
(Repair fielsystem) 1# ls /dev/sd*
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4
(Repair filesyatem) 1# ls /dev/hd*
ls: /dev/hd*: No such file or directory
Kindly suggest any configuration of windows server or kernel configs missing or how to resolve this issues
Many many thanks for your reply.
thanks & Regards,
Ujjwal

i am not able to understand duplicate UUID and from where it is picking /dev/hda* ?
~
VVM:>>
VVM:>> Output of dmesg | grep ata contain substring "Hyper-V" ?
VVM:>>
it doesn't contain "Hyper-V" or ata related message and the output doesn't change with boot parameter reserve=0x1f0, 0x8
~~
~~~~
==
output of dmesg related "ata" Ubuntu v13.04 mini.iso ( with boot parameter reserve=0x1f0, 0x8)
==
see later ( in "good situation" example )
~~
===
Disable legacy ATA driver by adding the following to kernel command line in /boot/grub/menu.lst:
reserve=0x1f0, 0x8
. (This option reserves this I/O region and prevents ata_piix from loading).
==
See output of dmesg related "ata" Ubuntu v13.04 mini.iso ( with boot parameter reserve=0x1f0, 0x8) :
~~
[ 0.176027]
libata version 3.00 loaded.
[ 0.713319]
ata_piix 0000:00:07.1: version 2.13
[ 0.713397]
ata_piix 0000:00:07.1: device not available (can't reserve [io 0x0000-0x0007])
[ 0.713404]
ata_piix: probe of 0000:00:07.1 failed with error -22
[ 0.713474]
pata_acpi 0000:00:07.1: device not available (can't reserve [io 0x0000-0x0007])
[ 0.713479]
pata_acpi: probe of 0000:00:07.1 failed with error -22
~~
As result: 1) IDE disk handled by hv_storvsc , but 2) no CD-ROM device
==
~ # blkid
/dev/sda1: LABEL="ARCH_BOOT" UUID="009c2043-4bl7-4f95-al4d-fb8951f95b5d" TYPE="ext2"
==
~~
VVM>>
VVM>>Q1: Output of blkid contain duplicate UUID ?
VVM>>
-> blkid contains duplicate UUID, below are the output.
~~
This situation is classic problem "
use hv_storvsc instead of ata_piix to handle the IDE disks devices ( but not for the DVD-ROM / CD-ROM device handling)
~~
For compare, see example "good situation":
See output of dmesg related "ata" Ubuntu v13.04 mini.iso ( without boot parameter reserve=0x1f0, 0x8) :
~~~~
~ # dmesg |grep ata
[ 0.167224] libata version 3.00 loaded.
[ 0.703109] ata_piix 0000:00:07.1: version 2.13
[ 0.703267] ata_piix 0000:00:07.1: Hyper-V Virtual Machine detected, ATA device ignore set
[ 0.703339] ata_piix 0000:00:07.1: setting latency timer to 64
[ 0.704968] scsi0 : ata_piix
[ 0.705713] scsi1 : ata_piix
[ 0.706191] atal: PATA max UDMA/33 cmd 0xlf0 ctl 0x3f6 bmdma 0xffa0 irq 14
[ 0.706194] ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
[ 0.868844] atal.00: host indicates ignore ATA devices, ignored
[ 0.869142] ata2.00: ATAPI: Virtual CD, , max MWDMA2
[ 0.871736] ata2.00: configured for MWDMA2
~~~~
===
~ # uname -a
Linux ubuntu 3.7.0-7-generic #15-Ubuntu SUP Sat Dec 15 14:13:08 UTC 2012 x86_64 GNU/Linux
~ # lsmod
hv_netvsc 22769 0
hv_storvsc 17496 3
hv_utils 13569 0
hv_vmbus 34432 3 hv_netvsc,hv_storvsc,hv_utils
~ # blkid
/dev/sr0: LABEL=”CDROM" TYPE="iso9660”
/dev/sda1: LABEL="ARCH_BOOT" UUID="009c2043-4bl7-4f95-al4d-fb8951f95b5d" TYPE="ext2"
===
( only CD-ROM and 1( one) IDE disk connected to ATA)
~~
regarding ata_piix.c patch . . .
As far as i understand this patch , it ignore ATA devices on Hyper-V when PV drivers(CONFIG_HYPERV_STORAGE=y) are enabled.
~~
Yes:
ignore ATA-HDD ( but not ignore ATA CD-ROM ) on Hyper-V when PV drivers(CONFIG_HYPERV_STORAGE=y) are enabled.
~
this patches need be backported:
cd006086fa5d ata_piix: defer disks to the Hyper-V drivers by default
and its prerequisite
db63a4c8115a libata: add a host flag to ignore detected ATA devices
~
~~
P.S.
Are You do this:
==
As temporary solution, increase on 1-2 Gb size all .vhd connected to IDE bus
( but not increase size of partitions inside disks)
==
? fsck write message a-la: "no error in file system" ?
2013-01-24 Answer by Ujjwal Kumar: As a temporary solution looks ok for me, but [ VVM: need true solution ]
P.P.S.
To Ujjwal Kumar :
My e-mail:
ZZZZZZZZZZZZZZZ
please send e-mail to me, in reply I send to You patches to ata_piix ( and *.c before and after patches) , etc.
} on 2013-01-14 -- DoNe

Remounting Root Filesystem Read-only, what for?

Hi.
I have question. What really for while rebooting/halting system root filesystem is remounted? One second before all filesystems are unmounted. Why it has to be mounted when shutting off the computer.
Thanks in advance.

alexpnx wrote:I have a question on a similar topic... How unsafe is it if the system is rebooted or shutdown without unmounting samba shares? Can the shares be corrupted?
I think the file(s) you're writing to during shutdown can be corrupted (not all corrupted, but simply unfinished saved), if you write there at all, but not anything else as the partition is still up on the host and the host takes care of metadata and stuff - it's worse with local partitions where metadata and stuff can be saved uncompletely, which can lead to files disappearing all over the filesystem, some old files showing up again etc.
Can someone else confirm this?

Btrfs root filesystem

The release notes for OL6.3 indicate that its possible to create a btrfs root filesystem on install using the alternative boot ISO media (excerpt from release notes at https://oss.oracle.com/ol6/docs/RELEASE-NOTES-U3-en.html):
Note: The standard installation media does not have support for creating a btrfs root filesystem on initial install. If you want to install Oracle Linux 6 Update 3 and use btrfs as your root filesystem, please use the alternative boot ISO media which uses btrfs as the default root filesystem. Using the boot.iso requires that the full installation source be available via a network method, i.e. FTP, HTTP or NFS.
However I still don't see how to do this. Just as with the full DVD install there isn't an option to use btrfs when laying out the fileystem in the installer. Anyone know how to do this?

Oracle Linux uses the RHEL 6 installer, which has no btrfs support. However, it is not difficult to convert your existing installation to btrfs. It takes only several minutes. You can boot the system from V33412-01 (Oracle 6.3 boot.iso) available from https://edelivery.oracle.com/linux
The following worked for me:
Start the system from Oracle 6.3 boot DVD
Select "Rescue installed system"
When prompted select "local cd/dvd" as installation source (we don't need it)
When prompted to start the network interface choose "no" (we don't need it)
When prompted "The rescue environment…." select "Skip"
Open "shell"
To find your system volume group, e.g. vg_vm003:
<pre>
vgscan
</pre>
Activate the LVM volume
<pre>
lvchange -ay vg_vm003
</pre>
To find your system partition (now ACTIVE), e.g. /dev/vg_vm003/lv_root
<pre>
lvscan
</pre>
Verify/Repair the filesystem and convert it to btrfs
<pre>
fsck -fy /dev/vg_vm003/lv_root
btrfs-convert /dev/vg_vm003/lv_root
</pre>
Mount the system partition (Do NOT use /mnt!)
<pre>
mkdir /me
mount /dev/vg_vm003/lv_root /me
</pre>
Modify fstab to change the fstype of your lv_root partition from "ext4" to "btrfs"
<pre>
vi /me/etc/fstab
</pre>
To address problems with SELinux, do the following to prevent "Respawning too fast. Stopped" errors at startup.
<pre>
touch /me/.autorelabel
</pre>
Finally dismount the partition
<pre>
umount /me
</pre>
Then remove the boot DVD and reset the computer. When the system restarts use default Oracle UEK kernel with btrfs support builtin.

[SOLVED] mkarchiso: ERROR: failed to detect root filesystem

hi guys!
i am now trying to build my own live archlinux distribution with archiso and with the command "mkarchiso"
at the first step in installing the base when it installs linux and execute "mkinitcpio" it shows me this error:
( 73/111) installing linux [#####################################################################] 100%
>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.9.9-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
==> ERROR: failed to detect root filesystem
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.9.9-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: aic94xx
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
i continue the process with that error and in the "run" step i did this command
# mkarchiso -w work/x86_64/ -r mkinitcpio -p linux run
[root@fuhrer livecd]# mkarchiso -w work/x86_64/ -r mkinitcpio -p linux run
[mkarchiso] INFO: Configuration settings
[mkarchiso] INFO: Command: run
[mkarchiso] INFO: Architecture: x86_64
[mkarchiso] INFO: Working directory: work/x86_64/
[mkarchiso] INFO: Installation directory: arch
[mkarchiso] INFO: Run command: mkinitcpio
==> Starting dry run: 3.9.9-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
==> ERROR: failed to detect root filesystem
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Dry run complete, use -g IMAGE to generate a real image
and the big problem shows when i build the iso file and "dd" it to USB disk, when i choose to boot the live archlinux it tell me
ERROR: failed to detect root filesystem
and that you cannot log to tty
any suggestions?
Last edited by fuhrer (2013-07-22 17:05:07)

First run it, without any modification to learn how it works. Check if works. Modify as you need. Check if works...
Do not worry about the mkinitcpio error, because such initramfs images should not be used for boot live medium. You can see that profiles uses own mkinitcpio.conf with at least archiso hook
Running mkarchiso directly is not the right way, at least if you do not know how things works.
[root@exequiel tmp]# cp -r /usr/share/archiso/configs/baseline .
[root@exequiel tmp]# cd baseline
[root@exequiel baseline]# ./build.sh
[mkarchiso] INFO: Configuration settings
[mkarchiso] INFO: Command: init
[mkarchiso] INFO: Architecture: x86_64
[mkarchiso] INFO: Working directory: work
[mkarchiso] INFO: Installation directory: arch
[mkarchiso] INFO: Pacman config file: /etc/pacman.conf
[mkarchiso] INFO: Installing packages to 'work/root-image/'...
:: Synchronizing package databases...
core 103.0 KiB 12.6M/s 00:00 [############################################################################] 100%
extra 1439.7 KiB 11.2M/s 00:00 [############################################################################] 100%
community 1990.1 KiB 11.2M/s 00:00 [############################################################################] 100%
multilib 107.3 KiB 11.6M/s 00:00 [############################################################################] 100%
:: There are 51 members in group base:
:: Repository core
1) bash 2) bzip2 3) coreutils 4) cronie 5) cryptsetup 6) device-mapper 7) dhcpcd 8) diffutils 9) e2fsprogs 10) file 11) filesystem 12) findutils 13) gawk 14) gcc-libs 15) gettext 16) glibc
17) grep 18) gzip 19) heirloom-mailx 20) inetutils 21) iproute2 22) iputils 23) jfsutils 24) less 25) licenses 26) linux 27) logrotate 28) lvm2 29) man-db 30) man-pages 31) mdadm 32) nano
33) netctl 34) pacman 35) pciutils 36) pcmciautils 37) perl 38) procps-ng 39) psmisc 40) reiserfsprogs 41) sed 42) shadow 43) sysfsutils 44) systemd-sysvcompat 45) tar 46) texinfo 47) usbutils
48) util-linux 49) vi 50) which 51) xfsprogs
Enter a selection (default=all):
resolving dependencies...
looking for inter-conflicts...
Packages (111):
Name New Version Net Change
core/acl 2.2.52-1 0.39 MiB
core/archlinux-keyring 20130525-2 0.49 MiB
core/attr 2.4.47-1 0.19 MiB
core/ca-certificates 20130610-1 0.25 MiB
core/cracklib 2.8.22-3 1.20 MiB
core/curl 7.31.0-1 1.73 MiB
core/db 5.3.21-1 15.30 MiB
core/dbus 1.6.12-1 1.63 MiB
core/dirmngr 1.1.1-1 0.49 MiB
core/expat 2.1.0-2 0.61 MiB
core/gdbm 1.10-1 0.37 MiB
core/glib2 2.36.3-2 11.66 MiB
core/gmp 5.1.2-1 2.07 MiB
core/gnupg 2.0.20-2 7.14 MiB
core/gpgme 1.4.2-1 0.68 MiB
core/groff 1.22.2-3 8.94 MiB
core/hwids 20130607-1 1.28 MiB
core/iana-etc 2.30-3 3.44 MiB
core/iptables 1.4.19.1-1 1.38 MiB
core/kbd 1.15.5-4 2.83 MiB
core/keyutils 1.5.5-5 0.18 MiB
core/kmod 14-1 0.45 MiB
core/krb5 1.11.3-1 3.86 MiB
core/libarchive 3.1.2-1 3.19 MiB
core/libassuan 2.1.1-1 0.17 MiB
core/libcap 2.22-5 0.13 MiB
core/libffi 3.0.13-3 0.10 MiB
core/libgcrypt 1.5.2-1 0.68 MiB
core/libgpg-error 1.12-1 0.33 MiB
core/libgssglue 0.4-1 0.19 MiB
core/libksba 1.3.0-1 0.30 MiB
core/libldap 2.4.35-4 2.15 MiB
core/libpipeline 1.2.4-1 0.08 MiB
core/libsasl 2.1.26-4 0.54 MiB
core/libssh2 1.4.3-1 1.19 MiB
core/libtirpc 0.2.3-1 0.68 MiB
core/libusbx 1.0.15-1 0.15 MiB
core/linux-api-headers 3.8.4-1 4.58 MiB
core/linux-firmware 20130610-1 51.25 MiB
core/lzo2 2.06-1 0.61 MiB
core/mkinitcpio 0.14.0-1 0.16 MiB
core/mkinitcpio-busybox 1.20.2-1 0.34 MiB
core/mpfr 3.1.2-1 1.50 MiB
core/ncurses 5.9-5 9.75 MiB
core/openresolv 3.5.5-1 0.04 MiB
core/openssl 1.0.1.e-3 11.38 MiB
core/pacman-mirrorlist 20130626-1 0.02 MiB
core/pam 1.1.6-4 3.41 MiB
core/pambase 20130113-1 0.04 MiB
core/pcre 8.33-1 4.83 MiB
core/pinentry 0.8.3-1 0.33 MiB
core/popt 1.16-6 0.43 MiB
core/pth 2.0.7-4 0.21 MiB
core/readline 6.2.004-1 1.20 MiB
core/run-parts 4.3.4-1 0.11 MiB
core/systemd 204-3 14.59 MiB
core/sysvinit-tools 2.88-11 0.07 MiB
core/tzdata 2013d-1 1.84 MiB
core/xz 5.0.5-1 0.90 MiB
core/zlib 1.2.8-1 0.30 MiB
core/bash 4.2.045-4 3.51 MiB
core/bzip2 1.0.6-4 0.25 MiB
core/coreutils 8.21-2 13.27 MiB
core/cronie 1.4.9-5 0.15 MiB
core/cryptsetup 1.6.1-2 0.71 MiB
core/device-mapper 2.02.98-4 0.52 MiB
core/dhcpcd 5.6.8-3 0.16 MiB
core/diffutils 3.3-1 0.43 MiB
core/e2fsprogs 1.42.8-1 3.16 MiB
core/file 5.14-1 2.71 MiB
core/filesystem 2013.05-2 0.01 MiB
core/findutils 4.4.2-5 1.70 MiB
core/gawk 4.1.0-1 2.11 MiB
core/gcc-libs 4.8.1-1 3.41 MiB
core/gettext 0.18.3-1 11.10 MiB
core/glibc 2.17-6 35.24 MiB
core/grep 2.14-2 1.33 MiB
core/gzip 1.6-1 0.18 MiB
core/heirloom-mailx 12.5-3 0.46 MiB
core/inetutils 1.9.1-6 0.97 MiB
core/iproute2 3.9.0-2 1.37 MiB
core/iputils 20121221-2 0.21 MiB
core/jfsutils 1.1.15-4 0.98 MiB
core/less 458-1 0.22 MiB
core/licenses 20130203-1 0.53 MiB
core/linux 3.9.9-1 63.98 MiB
core/logrotate 3.8.5-1 0.07 MiB
core/lvm2 2.02.98-4 3.10 MiB
core/man-db 2.6.5-1 1.26 MiB
core/man-pages 3.52-1 4.63 MiB
core/mdadm 3.2.6-4 1.18 MiB
core/nano 2.2.6-2 1.49 MiB
core/netctl 1.1-1 0.16 MiB
core/pacman 4.1.2-1 4.04 MiB
core/pciutils 3.2.0-3 0.34 MiB
core/pcmciautils 018-7 0.05 MiB
core/perl 5.18.0-1 47.64 MiB
core/procps-ng 3.3.8-2 0.59 MiB
core/psmisc 22.20-1 0.73 MiB
core/reiserfsprogs 3.6.23-1 0.95 MiB
core/sed 4.2.2-3 0.76 MiB
core/shadow 4.1.5.1-6 3.88 MiB
core/sysfsutils 2.1.0-8 0.17 MiB
core/systemd-sysvcompat 204-3 0.03 MiB
core/tar 1.26-4 2.33 MiB
core/texinfo 5.1-1 8.62 MiB
core/usbutils 007-1 0.17 MiB
core/util-linux 2.23.1-2 8.92 MiB
core/vi 1:050325-3 0.33 MiB
core/which 2.20-6 0.06 MiB
core/xfsprogs 3.1.11-1 3.29 MiB
Total Installed Size: 427.79 MiB
:: Proceed with installation? [Y/n]
(111/111) checking keys in keyring [############################################################################] 100%
(111/111) checking package integrity [############################################################################] 100%
(111/111) loading package files [############################################################################] 100%
(111/111) checking for file conflicts [############################################################################] 100%
(111/111) checking available disk space [############################################################################] 100%
( 1/111) installing linux-api-headers [############################################################################] 100%
( 2/111) installing tzdata [############################################################################] 100%
( 3/111) installing iana-etc [############################################################################] 100%
( 4/111) installing filesystem [############################################################################] 100%
warning: directory permissions differ on /tmp/baseline/work/root-image/run/
filesystem: 1777 package: 755
( 5/111) installing glibc [############################################################################] 100%
( 6/111) installing ncurses [############################################################################] 100%
( 7/111) installing readline [############################################################################] 100%
( 8/111) installing bash [############################################################################] 100%
( 9/111) installing bzip2 [############################################################################] 100%
( 10/111) installing gcc-libs [############################################################################] 100%
( 11/111) installing db [############################################################################] 100%
( 12/111) installing zlib [############################################################################] 100%
( 13/111) installing cracklib [############################################################################] 100%
( 14/111) installing libgssglue [############################################################################] 100%
( 15/111) installing libtirpc [############################################################################] 100%
( 16/111) installing pambase [############################################################################] 100%
( 17/111) installing pam [############################################################################] 100%
( 18/111) installing attr [############################################################################] 100%
( 19/111) installing acl [############################################################################] 100%
( 20/111) installing gmp [############################################################################] 100%
( 21/111) installing libcap [############################################################################] 100%
( 22/111) installing coreutils [############################################################################] 100%
( 23/111) installing run-parts [############################################################################] 100%
( 24/111) installing cronie [############################################################################] 100%
Optional dependencies for cronie
pm-utils: defer anacron on battery power
smtp-server: send job output via email
smtp-forwarder: forward job output to email server
( 25/111) installing expat [############################################################################] 100%
( 26/111) installing dbus [############################################################################] 100%
Optional dependencies for dbus
libx11: dbus-launch support
( 27/111) installing pcre [############################################################################] 100%
( 28/111) installing libffi [############################################################################] 100%
( 29/111) installing glib2 [############################################################################] 100%
Optional dependencies for glib2
python2: for gdbus-codegen and gtester-report
elfutils: gresource inspection tool
( 30/111) installing kbd [############################################################################] 100%
( 31/111) installing kmod [############################################################################] 100%
( 32/111) installing hwids [############################################################################] 100%
( 33/111) installing libgpg-error [############################################################################] 100%
( 34/111) installing libgcrypt [############################################################################] 100%
( 35/111) installing shadow [############################################################################] 100%
( 36/111) installing util-linux [############################################################################] 100%
( 37/111) installing xz [############################################################################] 100%
( 38/111) installing systemd [############################################################################] 100%
Initializing machine ID from random generator.
ln -s '/usr/lib/systemd/system/[email protected]' '/etc/systemd/system/getty.target.wants/[email protected]'
:: Append 'init=/usr/lib/systemd/systemd' to your kernel command line in your
bootloader to replace sysvinit with systemd, or install systemd-sysvcompat
Optional dependencies for systemd
cryptsetup: required for encrypted block devices [pending]
libmicrohttpd: systemd-journal-gatewayd
quota-tools: kernel-level quota management
python: systemd library bindings
systemd-sysvcompat: symlink package to provide sysvinit binaries [pending]
( 39/111) installing device-mapper [############################################################################] 100%
( 40/111) installing popt [############################################################################] 100%
( 41/111) installing cryptsetup [############################################################################] 100%
( 42/111) installing dhcpcd [############################################################################] 100%
( 43/111) installing diffutils [############################################################################] 100%
( 44/111) installing e2fsprogs [############################################################################] 100%
( 45/111) installing file [############################################################################] 100%
( 46/111) installing findutils [############################################################################] 100%
( 47/111) installing mpfr [############################################################################] 100%
( 48/111) installing gawk [############################################################################] 100%
( 49/111) installing gettext [############################################################################] 100%
Optional dependencies for gettext
cvs: for autopoint tool
( 50/111) installing grep [############################################################################] 100%
( 51/111) installing less [############################################################################] 100%
( 52/111) installing gzip [############################################################################] 100%
( 53/111) installing gdbm [############################################################################] 100%
( 54/111) installing perl [############################################################################] 100%
( 55/111) installing openssl [############################################################################] 100%
Optional dependencies for openssl
ca-certificates [pending]
( 56/111) installing libsasl [############################################################################] 100%
( 57/111) installing libldap [############################################################################] 100%
( 58/111) installing keyutils [############################################################################] 100%
( 59/111) installing krb5 [############################################################################] 100%
( 60/111) installing heirloom-mailx [############################################################################] 100%
Optional dependencies for heirloom-mailx
smtp-forwarder: for sending mail
( 61/111) installing inetutils [############################################################################] 100%
( 62/111) installing iptables [############################################################################] 100%
( 63/111) installing iproute2 [############################################################################] 100%
Optional dependencies for iproute2
linux-atm: ATM support
( 64/111) installing sysfsutils [############################################################################] 100%
( 65/111) installing iputils [############################################################################] 100%
Optional dependencies for iputils
xinetd: for tftpd
( 66/111) installing jfsutils [############################################################################] 100%
( 67/111) installing licenses [############################################################################] 100%
( 68/111) installing linux-firmware [############################################################################] 100%
( 69/111) installing mkinitcpio-busybox [############################################################################] 100%
( 70/111) installing lzo2 [############################################################################] 100%
( 71/111) installing libarchive [############################################################################] 100%
( 72/111) installing mkinitcpio [############################################################################] 100%
Optional dependencies for mkinitcpio
xz: Use lzma or xz compression for the initramfs image [pending]
bzip2: Use bzip2 compression for the initramfs image [pending]
lzop: Use lzo compression for the initramfs image
mkinitcpio-nfs-utils: Support for root filesystem on NFS
( 73/111) installing linux [############################################################################] 100%
>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.9.9-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
==> ERROR: failed to detect root filesystem
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.9.9-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: aic94xx
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
Optional dependencies for linux
crda: to set the correct wireless channels of your country
( 74/111) installing logrotate [############################################################################] 100%
Optional dependencies for logrotate
cron: scheduled log rotation
( 75/111) installing lvm2 [############################################################################] 100%
( 76/111) installing groff [############################################################################] 100%
Optional dependencies for groff
netpbm: for use together with man -H command interaction in browsers
psutils: for use together with man -H command interaction in browsers
libxaw: for gxditview
( 77/111) installing libpipeline [############################################################################] 100%
( 78/111) installing man-db [############################################################################] 100%
it's recommended to create an initial
database running as root:
"/usr/bin/mandb --quiet"
Optional dependencies for man-db
gzip [pending]
( 79/111) installing man-pages [############################################################################] 100%
( 80/111) installing mdadm [############################################################################] 100%
( 81/111) installing nano [############################################################################] 100%
( 82/111) installing openresolv [############################################################################] 100%
( 83/111) installing netctl [############################################################################] 100%
Optional dependencies for netctl
dialog: for the menu based wifi assistant
dhclient: for DHCP support (or dhcpcd)
dhcpcd: for DHCP support (or dhclient) [pending]
wpa_supplicant: for wireless networking support
ifplugd: for automatic wired connections through netctl-ifplugd
wpa_actiond: for automatic wireless connections through netctl-auto
ifenslave: for bond connections
bridge-utils: for bridge connections
ppp: for pppoe connections
( 84/111) installing sed [############################################################################] 100%
( 85/111) installing ca-certificates [############################################################################] 100%
( 86/111) installing libssh2 [############################################################################] 100%
( 87/111) installing curl [############################################################################] 100%
( 88/111) installing pth [############################################################################] 100%
( 89/111) installing libksba [############################################################################] 100%
( 90/111) installing libassuan [############################################################################] 100%
( 91/111) installing pinentry [############################################################################] 100%
Optional dependencies for pinentry
gtk2: for gtk2 backend
qt4: for qt4 backend
( 92/111) installing dirmngr [############################################################################] 100%
( 93/111) installing gnupg [############################################################################] 100%
Optional dependencies for gnupg
curl: gpg2keys_curl [pending]
libldap: gpg2keys_ldap [pending]
libusb-compat: scdaemon
( 94/111) installing gpgme [############################################################################] 100%
( 95/111) installing pacman-mirrorlist [############################################################################] 100%
( 96/111) installing archlinux-keyring [############################################################################] 100%
( 97/111) installing pacman [############################################################################] 100%
>>> Run `pacman-key --init; pacman-key --populate archlinux`
>>> to import the data required by pacman for package verification.
>>> See: https://www.archlinux.org/news/having-pacman-verify-packages
Optional dependencies for pacman
fakeroot: for makepkg usage as normal user
( 98/111) installing pciutils [############################################################################] 100%
( 99/111) installing pcmciautils [############################################################################] 100%
(100/111) installing procps-ng [############################################################################] 100%
(101/111) installing psmisc [############################################################################] 100%
(102/111) installing reiserfsprogs [############################################################################] 100%
(103/111) installing sysvinit-tools [############################################################################] 100%
(104/111) installing systemd-sysvcompat [############################################################################] 100%
(105/111) installing tar [############################################################################] 100%
(106/111) installing texinfo [############################################################################] 100%
(107/111) installing libusbx [############################################################################] 100%
(108/111) installing usbutils [############################################################################] 100%
Optional dependencies for usbutils
python2: for lsusb.py usage
coreutils: for lsusb.py usage [pending]
(109/111) installing vi [############################################################################] 100%
Optional dependencies for vi
heirloom-mailx: used by the preserve command for notification [pending]
(110/111) installing which [############################################################################] 100%
(111/111) installing xfsprogs [############################################################################] 100%
[mkarchiso] INFO: Packages installed successfully!
[mkarchiso] INFO: Installing packages to 'work/root-image/'...
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
resolving dependencies...
looking for inter-conflicts...
Packages (1):
Name New Version Net Change
core/syslinux 4.06-2 3.35 MiB
Total Installed Size: 3.35 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [############################################################################] 100%
(1/1) checking package integrity [############################################################################] 100%
(1/1) loading package files [############################################################################] 100%
(1/1) checking for file conflicts [############################################################################] 100%
(1/1) checking available disk space [############################################################################] 100%
(1/1) installing syslinux [############################################################################] 100%
==> If you want to use syslinux as your bootloader
==> edit /boot/syslinux/syslinux.cfg and run
==> # /usr/bin/syslinux-install_update -i -a -m
==> to install it.
Optional dependencies for syslinux
perl-passwd-md5: For md5pass
perl-digest-sha1: For sha1pass
mtools: For mkdiskimage and syslinux support
gptfdisk: For GPT support
util-linux: For isohybrid [installed]
[mkarchiso] INFO: Packages installed successfully!
[mkarchiso] INFO: Configuration settings
[mkarchiso] INFO: Command: run
[mkarchiso] INFO: Architecture: x86_64
[mkarchiso] INFO: Working directory: work
[mkarchiso] INFO: Installation directory: arch
[mkarchiso] INFO: Run command: mkinitcpio -c /etc/mkinitcpio-archiso.conf -k /boot/vmlinuz-linux -g /boot/archiso.img
==> Starting build: 3.9.9-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [archiso]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: aic94xx
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/archiso.img
==> Image generation successful
[mkarchiso] INFO: Configuration settings
[mkarchiso] INFO: Command: prepare
[mkarchiso] INFO: Architecture: x86_64
[mkarchiso] INFO: Working directory: work
[mkarchiso] INFO: Installation directory: arch
[mkarchiso] INFO: Cleaning up what we can on root-image...
[mkarchiso] INFO: Done!
[mkarchiso] INFO: Target 'work/iso/arch/x86_64/root-image.fs.sfs' does not exist, making it from 'work/root-image'
[mkarchiso] INFO: Creating ext4 image of 1025 MiB...
mke2fs 1.42.8 (20-Jun-2013)
Discarding device blocks: done
warning: 256 blocks unused.
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
65664 inodes, 262144 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=268435456
8 block groups
32768 blocks per group, 32768 fragments per group
8208 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376
Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
[mkarchiso] INFO: Done!
[mkarchiso] INFO: Mounting 'work/root-image.fs' on 'work/mnt/root-image'
[mkarchiso] INFO: Total: 1008 MiB (100%) | Used: 2 MiB (1%) | Avail: 1007 MiB (99%)
[mkarchiso] INFO: Copying 'work/root-image/' to 'work/mnt/root-image/'...
[mkarchiso] INFO: Done!
[mkarchiso] INFO: Total: 1008 MiB (100%) | Used: 552 MiB (55%) | Avail: 457 MiB (45%)
[mkarchiso] INFO: Unmounting 'work/mnt/root-image'
[mkarchiso] INFO: Creating SquashFS image for 'work/root-image.fs', This may take some time...
Parallel mksquashfs: Using 2 processors
Creating 4.0 filesystem on work/root-image.fs.sfs, block size 131072.
Exportable Squashfs 4.0 filesystem, gzip compressed, data block size 131072
compressed data, compressed metadata, compressed fragments, compressed xattrs
duplicates are removed
Filesystem size 193188.71 Kbytes (188.66 Mbytes)
18.41% of uncompressed filesystem size (1049632.29 Kbytes)
Inode table size 10918 bytes (10.66 Kbytes)
33.19% of uncompressed inode table size (32898 bytes)
Directory table size 31 bytes (0.03 Kbytes)
88.57% of uncompressed directory table size (35 bytes)
Number of duplicate files found 0
Number of inodes 2
Number of files 1
Number of fragments 0
Number of symbolic links 0
Number of device nodes 0
Number of fifo nodes 0
Number of socket nodes 0
Number of directories 1
Number of ids (unique uids + gids) 1
Number of uids 1
root (0)
Number of gids 1
root (0)
[mkarchiso] INFO: Image creation done in 01:46 minutes
[mkarchiso] INFO: Configuration settings
[mkarchiso] INFO: Command: checksum
[mkarchiso] INFO: Architecture: x86_64
[mkarchiso] INFO: Working directory: work
[mkarchiso] INFO: Installation directory: arch
[mkarchiso] INFO: Target 'work/iso/arch/checksum.i686.md5' does not exist, making it from 'work/iso/arch'
[mkarchiso] INFO: Creating checksum file for self-test (i686)...
[mkarchiso] INFO: Done!
[mkarchiso] INFO: Target 'work/iso/arch/checksum.x86_64.md5' does not exist, making it from 'work/iso/arch'
[mkarchiso] INFO: Creating checksum file for self-test (x86_64)...
[mkarchiso] INFO: Done!
[mkarchiso] INFO: Configuration settings
[mkarchiso] INFO: Command: iso
[mkarchiso] INFO: Architecture: x86_64
[mkarchiso] INFO: Working directory: work
[mkarchiso] INFO: Installation directory: arch
[mkarchiso] INFO: Image name: archlinux-2013.07.21-x86_64.iso
[mkarchiso] INFO: Disk label: ARCH_201307
[mkarchiso] INFO: Disk publisher: Arch Linux <http://www.archlinux.org>
[mkarchiso] INFO: Disk application: Arch Linux Live/Rescue CD
[mkarchiso] INFO: Target 'out/archlinux-2013.07.21-x86_64.iso' does not exist, making it from 'work/iso'
[mkarchiso] INFO: Creating ISO image...
xorriso 1.3.0 : RockRidge filesystem manipulator, libburnia project.
Drive current: -outdev 'stdio:out/archlinux-2013.07.21-x86_64.iso'
Media current: stdio file, overwriteable
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 4155m free
Added to ISO image: directory '/'='/tmp/baseline/work/iso'
xorriso : UPDATE : 16 files added in 1 seconds
xorriso : UPDATE : 16 files added in 1 seconds
xorriso : NOTE : Copying to System Area: 432 bytes from file '/tmp/baseline/work/iso/isolinux/isohdpfx.bin'
libisofs: NOTE : Aligned image size to cylinder size by 177 blocks
xorriso : UPDATE : 16.90% done
xorriso : UPDATE : 82.85% done
ISO image produced: 105472 sectors
Written to medium : 105472 sectors at LBA 0
Writing to 'stdio:out/archlinux-2013.07.21-x86_64.iso' completed successfully.
[mkarchiso] INFO: Done! | 206M out/archlinux-2013.07.21-x86_64.iso
Booting:
:: running early hook [udev]
:: running hook [udev]
:: Triggering uevents...
:: running hook [archiso]
:: Mounting '/dev/disk/by-label/ARCH_201307' to '/run/archiso/bootmnt'
:: Device '/dev/disk/by-label/ARCH_201307' mounted successfully.
:: Mounting /run/archiso/cowspace (tmpfs) filesystem, size=75%...
:: Mounting '/dev/loop0' to '/run/archiso/sfs/root-image'
:: Device '/dev/loop0' mounted successfully.
:: Creating '/run/archiso/cowspace/persistent_ARCH_201307/x86_64/root-image.cow' as non-persistent.
:: Mounting '/dev/mapper/arch_root-image' to '/new_root/'
:: Device '/dev/mapper/arch_root-image' mounted successfully.
:: running cleanup hook [udev]
Welcome to Arch Linux!
Expecting device dev-ttyS0.device...
[ OK ] Reached target Remote File Systems.
[ OK ] Listening on LVM2 metadata daemon socket.
[ OK ] Listening on Device-mapper event daemon FIFOs.
[ OK ] Listening on Delayed Shutdown Socket.
[ OK ] Listening on /dev/initctl Compatibility Named Pipe.
[ OK ] Listening on udev Kernel Socket.
[ OK ] Listening on udev Control Socket.
[ OK ] Reached target Paths.
[ OK ] Reached target Encrypted Volumes.
[ OK ] Set up automount Arbitrary Executable File Formats F...utomount Point.
[ OK ] Listening on Journal Socket.
Mounting POSIX Message Queue File System...
Starting Setup Virtual Console...
Starting Create static device nodes in /dev...
Mounting Huge Pages File System...
Starting Apply Kernel Variables...
Mounting Debug File System...
Mounting Configuration File System...
Starting udev Coldplug all Devices...
Starting Journal Service...
[ OK ] Started Journal Service.
[ OK ] Reached target Swap.
Mounting Temporary Directory...
Starting Remount Root and Kernel File Systems...
[ OK ] Mounted POSIX Message Queue File System.
[ OK ] Started Remount Root and Kernel File Systems.
[ OK ] Started Setup Virtual Console.
[ OK ] Started Apply Kernel Variables.
[ OK ] Mounted Huge Pages File System.
[ OK ] Mounted Debug File System.
[ OK ] Started Create static device nodes in /dev.
[ OK ] Mounted Configuration File System.
[ OK ] Mounted Temporary Directory.
Starting udev Kernel Device Manager...
Starting Load Random Seed...
[ OK ] Started Load Random Seed.
[ OK ] Started udev Kernel Device Manager.
[ OK ] Reached target Local File Systems (Pre).
[ OK ] Reached target Local File Systems.
Starting Trigger Flushing of Journal to Persistent Storage...
Starting Recreate Volatile Files and Directories...
[ OK ] Started udev Coldplug all Devices.
[ OK ] Started Recreate Volatile Files and Directories.
Starting Update UTMP about System Reboot/Shutdown...
[ OK ] Started Trigger Flushing of Journal to Persistent Storage.
[ OK ] Started Update UTMP about System Reboot/Shutdown.
[ OK ] Reached target System Initialization.
[ OK ] Reached target Timers.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
Starting Permit User Sessions...
Starting D-Bus System Message Bus...
[ OK ] Started D-Bus System Message Bus.
Starting Login Service...
[ OK ] Started Permit User Sessions.
Starting Getty on tty1...
[ OK ] Started Getty on tty1.
[ OK ] Started Login Service.
[ OK ] Found device /dev/ttyS0.
Starting Serial Getty on ttyS0...
[ OK ] Started Serial Getty on ttyS0.
[ OK ] Reached target Login Prompts.
[ OK ] Reached target Multi-User System.
[ OK ] Reached target Graphical Interface.
Arch Linux 3.9.9-1-ARCH (ttyS0)
localhost login:

Recommended maintance in a xfs/ext4 filesystem

What kind of "good practices" are recommended do in linux, in a XFS (root) and EXT4 (home) filesystems to mantain the system 'always ready'?
In a raid array, as wiki says, a good practice would be regularly scrubbing, but in a "not RAID" system, what kind of utilities may I use to mantain ok my system?

If you're not using RAID then I will assume this is not a production server you're running But for any and all systems I recommended backup backup backup and back up your backups, and test that they work!
e2fsck seems like a good tool, and it's GPLv2. Just read the manual thoroughly!
Last edited by ingegnue (2014-10-01 03:09:44)

[SOLVED] df -h does not reflect true root filesystem size

Why does df -h show root filesystem as being only 20G?
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/cryptroot 20G 15G 4.6G 76% /
dev 7.7G 0 7.7G 0% /dev
run 7.7G 668K 7.7G 1% /run
tmpfs 7.7G 70M 7.7G 1% /dev/shm
tmpfs 7.7G 0 7.7G 0% /sys/fs/cgroup
tmpfs 7.7G 224K 7.7G 1% /tmp
/dev/sda1 239M 40M 183M 18% /boot
tmpfs 1.6G 8.0K 1.6G 1% /run/user/1000
That is what my df -h output looks like. My setup is full disk encryption using dm-crypt with LUKS, per the guide on arch wiki. I basically created one /boot partition and left the rest of the disk to be an encrypted partition for the root filesystem. So why is my system complaining about (and acting as if it's running out of space)? Have I forgotten something?
Thank you for reading this. Let me know if you need any more logs or info on my setup - I realise I haven't provided very much info here, but I can't think of what to provide.
Last edited by domentoi (2014-12-24 19:02:32)

This is lsblk:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 250M 0 part /boot
└─sda2 8:2 0 465.5G 0 part
└─cryptroot 254:0 0 465.5G 0 crypt /
sdb 8:16 0 14.9G 0 disk
└─sdb1 8:17 0 14.9G 0 part
and fdisk -l
Disk /dev/sdb: 14.9 GiB, 16013942784 bytes, 31277232 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x5da5572f
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 31275007 31272960 14.9G 73 unknown
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xa5018820
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 514047 512000 250M 83 Linux
/dev/sda2 514048 976773167 976259120 465.5G 83 Linux
Disk /dev/mapper/cryptroot: 465.5 GiB, 499842572288 bytes, 976255024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sdc: 1.4 TiB, 1500301908480 bytes, 2930277165 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x445e51a8
And graysky: I thought I made the partition for /boot 250 MB and the encrypted partition 465.5 GB but I'm now quite sure I did something wrong...
Thank you all

After upgrading to Solaris 10 "Can't load the root filesystem" on V245

I have a Sunfire V245 that was running on Solaris 9 (very stable). I upgraded to Solaris 10 (6/06) this morning and everything seemed to go smoothly. After the upgrade the system rebooted, but will not boot. I get the following uptput;
Rebooting with command: boot
Boot device: disk File and args:
SunOS Release 5.10 Version Generic_118833-17 64-bit
Copyright 1983-2005 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
pxb_bcm: cannot load driver
Cannot load drivers for /pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/disk@0,0:a
Can't load the root filesystem
Type 'go' to resume
"go" attempts to reboot, but I end up back in the same place.
Please help.
Thanks in advanced,
Craig

It seems like the driver for that device does not exist. Since the system installed successfully it means that it S10 did find a disk. I wonder if that was a different disk than the default disk. Please boot to the miniroot and check the disk info.

Moving root filesystem to another hard drive

Hi everyone,
I've been using Arch Linux for a few months now and it is by far my favorite Linux distribution.
I currently have Arch on an old Pentium III, with a whopping 20 GB IDE hard drive.
I'm building a new computer, and want to use a larger 160 GB SATA hard drive, and I was wondering what is the best way that I can just transfer my entire root filesystem so I don't have to bother copying all the scripts, programs, etc.
Can I just tarball my root directory, partition my new hard drive, and use some other LiveCD to copy the root partition? I know this shouldn't be that difficult, because everything in the root partition is in /, unlike Windows, which has association problems with the registry.
Thanks!

I'd never want to lead anyone down the garden path without at least trying this myself so for the last hour or so I've done just as described above on an old computer I have that I play around with and a spare small 8 gb hard drive. I first tried copying the files over with thunar but that didn't work too well (froze up) probably due to trying to copy /sys and /proc--duh.
I tried again using midnight commander (to install do #pacman -S mc) and it worked perfectly. The /dev directory copied over just fine but don't try copying /proc and /sys. Just make empty directories so the system can put what it needs there. Also just make an empty /mnt directory and put your devices in later--otherwise I'm not sure what would happen if you were copying your /mnt/newroot to itself, but I'm sure it wouldn't be good.
I tried to just install grub on the slave with #grub-install /dev/sdb and it said it installed fine but when I switched the slave to master and disconnected the old master, grub wouldn't boot (probably because it was installed to /dev/sdb?) so I had to use the arch install disk to install grub. Then, much to my surprise--like I had any doubts--I rebooted and now I'm posting this with the newly copied Arch with xfce4.
It might not be a bad idea to backup any really important stuff but you are just copying and unless you do something silly, everything should work fine.
Last edited by bgc1954 (2008-03-11 23:13:58)

Kinit mounts root filesystem as read only [HELP][solved]

hello
I've being messing around with my mkinitcpio trying to optimize my boot speed, i removed some of the hooks at the beginning i couldn't boot, but then now i can boot but the root filesystem mounts as read only, i tried everything my fstab looks fine, / exists with defaults i tried to mount it referencing by it's uuid or by it's name and i get the same results, it mounts the filesystem as root only all the time no mather what i do.
There is not logs since i started playing with mkinitcpio, or anything i searched everywhere in this forum and around the internet, and i can't find any solution that would work, i restored all the hooks and modules on mkinitcpio and the result it's still the same. i also changed the menu.lst in grub to vga=773 but that's about it.
Can anyone help with this please i can't seem to boot properly.
Regards
Last edited by ricardoduarte (2008-09-14 16:16:25)

Hello
Basically what happens it's that it loads all the uDev events then the loopback, it mounts the root read only, then when it checks filesystems it says
/dev/sda4: clean, 205184/481440 files, 1139604/1920356 blocks [fail]
************FILESYSTEM CHECK FAILED****************
* Please repair manually and reboot. Note that the root *
* file system is currently mounted read-only. To remount *
* it read-write: mount -n -o remount,rw / *
* When you exit the maintenance shell the will *
* reboot automatically. *
Now what bugs me its that i can do that mount -n -o remount,rw / with no problems and when i do
e2fsck -f /dev/sda4
it doesn't return any errors just says that 0.9 non continuous.
none of this makes sense to me!! thats why i though that the problem could be coming from mkinitcpio or something
any ideas
Thanks for your help, btw thanks for the quick reply
Regards
Last edited by ricardoduarte (2008-09-14 15:48:49)

ZFS root filesystem & slice 7 for metadb (SUNWjet)

Hi,
I'm planning to use ZFS root filesystem in Sun Cluster 3.3 environment, as written in documentation when we will use UFS share diskset then we need to create small slice for metadb on slice 7. In standar installation we can't create slice 7 when we install solaris with zfs root, then we can create it with jumpstart profile below :
# example Jumpstart profile -- ZFS with
# space on s7 left out of the zpool for SVM metadb
install_type initial_install
cluster SUNWCXall
filesys c0t0d0s7 32
pool rpool auto 2G 2G c0t0d0s0
so, my question is : "when we use SUNWjet (JumpStart(tm) Enterprise Toolkit) how we can write the profile similar to above jumpstart profile"?
Thanks very much, for your best answer.

This can be done with JET
You create the template as normal.
Then create a profile file with the slice 7 line.
Then edit the template to use it.
see
---8<
# It is also possible to append additional profile information to the JET
# derived one. Do this using the base_config_profile_append variable, but
# don't forget to fill out the remaining base_config_profile variables.
base_config_profile=""
base_config_profile_append="
---8<
It is how OpsCentre (which uses JET) does it.
JET questions are best asked on the external JET alias at yahoogorups (until the forum is setup on OTN)

[Solved] NFS shares root filesystem

[edit] Sorry, my fault. I was using Nautilus m(
and i think it silently switiched to using sftp.... still wondering why no password was prompted.
Hi!
I set up nfs following the wiki. It works, but i can access the whole remote-root-filesystem, not just the nfs-root. Is https://wiki.archlinux.org/index.php/NFS up to date?
greetings
Server:
cat /etc/exports
/srv/nfs4/ 192.168.0.0/24(ro,fsid=0,no_subtree_check)
/srv/nfs4/a 192.168.0.0/24(ro,no_subtree_check)
/srv/nfs4/b 192.168.0.0/24(ro,no_subtree_check)
[root@alarmpi srv]#
Client:
showmount -e 192.168.0.116
Export list for 192.168.0.116:
/srv/nfs4/a 192.168.0.0/24
/srv/nfs4/b 192.168.0.0/24
/srv/nfs4 192.168.0.0/24
Last edited by matto (2015-03-22 14:50:59)

Thanks for the hints. Meanwhile, I have done some more background reading on running Arch in VMWare Player. In particular I followed the guidelines in this article. So it turns out that X requires some special configuration when run from within VMWare.
pacman -S xf86-input-vmmouse xf86-video-vmware xf86-video-vesa svga-dri
and a vmwgfx module is supposed to be loaded. I installed tha packages and tried to load vmwgfx, but when I do lsmod I just can't see it. Then it was pointed out to me that it might be a kernel mismatch problem. The linux installed on nfsroot is 3.6.2 whereas for some reason uname -a gives me version 3.5.6.
I've tried to rebuild initramfs with the new kernel using -k switch of mkinicpio, but it didn't help. It still boots into 3.5.6. It as if the initramfs from the client was taking precedence. So then I went back to the previous image of my VM, updated the system, made appropriate changes to mkinitcpio.conf and run mkinitcpio... and it no longer boots. mount: protocol not supported. I will post the details in my other topic.

"ludowngrade" - Sol 8 root filesystem trashed after mounting on Sol 10?

I've been giving liveupgrade a shot and it seems to work well for upgrading Sol 8 to Sol 10 until a downgrade / rollback is attempted.
To make a long story short, luactivating back to the old Sol 8 instance doesn't work because I haven't figured out a way to completely unencapsulate the Sol 8 SVM root metadevice without completely removing all SVM metadevices and metadbs from the system before the luupgrade, and we can only reboot once, to activate the newupgrade.
This leaves the old Sol 8 root filesystem metadevice around after the upgrade (even though it is not mounted anywhere). After an luactivate back to the Sol 8 instance, something gets set wrong and the 5.8 kernel panics with all kinds of undefined symbol errors.
Which leaves me no choice but to reboot in Solaris 10, and mount the old Solaris 8 filesystem, then edit the Sol 8 /etc/system and vfstab files to boot off a plain, non-SVM root filesystem.
Here's the problem: Once I have mounted the Old Sol 8 filesystem in Sol 10, it fails fsck when booting Sol 8;
/dev/rdsk/c1t0d0s0: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
# fsck /dev/rdsk/c1t0d0s0
BAD SUPERBLOCK AT BLOCK 16: BAD VALUES IN SUPER BLOCK
LOOK FOR ALTERNATE SUPERBLOCKS WITH MKFS? y
USE ALTERNATE SUPERBLOCK? y
FOUND ALTERNATE SUPERBLOCK AT 32 USING MKFS
CANCEL FILESYSTEM CHECK? n
Fortunately, recovering the alternate superblock makes the filesystem usable in Sol 8 again. Is this supposed to happen?
The only thing I can think of is I have logging enabled on the root FS in Sol 10, so apparently logging trashes the superblock in Sol 10 such that the FS cannot be mounted in Sol 8 without repair.
Better yet would be a HOWTO on how to luupgrade a root filesystem encapsulated in SVM without removing the metadevices first. It seems impossible since without any fiddling, all the LU instances on the host will share the SVM metadb's on the system, which leads to problems.

Did you upgrade the version of powerpath to a release supported on Solaris 10?

XFS Root Filesystem on LVM Stripe - Corruption

Similar Messages

Maybe you are looking for