Manage btrfs snapshots

One of the feature that i much like about btrfs is Snapshot.
What i want to do is to create snapshots of /home every 5/15 minutes (i have to test better the impact on performance) and retain:
02 - Yearly snapshots
12 - Monthly snapshots
16 - Weekly snapshots
28 - Daily snapshots
48 - Hourly snapshots
60 - Minutely snapshots
The above scheme is indicative and i'm looking for suggestion in order to improve  it.
After long google searching finally i've found a very simple but powerful bash script to manage btrfs snapshots: https://github.com/mmehnert/btrfs-snapshot-rotation
I've changed a bit the script in order to use my naming scheme
#!/bin/bash
# Parse arguments:
SOURCE=$1
TARGET=$2
SNAP=$3
COUNT=$4
QUIET=$5
# Function to display usage:
usage() {
scriptname=`/usr/bin/basename $0`
cat <<EOF
$scriptname: Take and rotate snapshots on a btrfs file system
Usage:
$scriptname source target snap_name count [-q]
source: path to make snaphost of
target: snapshot directory
snap_name: Base name for snapshots, to be appended to
date "+%F--%H-%M-%S"
count: Number of snapshots in the timestamp-@snap_name format to
keep at one time for a given snap_name.
[-q]: Be quiet.
Example for crontab:
15,30,45 * * * * root /usr/local/bin/btrfs-snapshot /home /home/__snapshots quarterly 4 -q
0 * * * * root /usr/local/bin/btrfs-snapshot /home /home/__snapshots hourly 8 -q
Example for anacrontab:
1 10 daily_snap /usr/local/bin/btrfs-snapshot /home /home/__snapshots daily 8
7 30 weekly_snap /usr/local/bin/btrfs-snapshot /home /home/__snapsnots weekly 5
@monthly 90 monthly_snap /usr/local/bin/btrfs-snapshot /home /home/__snapshots monthly 3
EOF
exit
# Basic argument checks:
if [ -z $COUNT ] ; then
echo "COUNT is not provided."
usage
fi
if [ ! -z $6 ] ; then
echo "Too many options."
usage
fi
if [ -n "$QUIET" ] && [ "x$QUIET" != "x-q" ] ; then
echo "Option 4 is either -q or empty. Given: \"$QUIET\""
usage
fi
# $max_snap is the highest number of snapshots that will be kept for $SNAP.
max_snap=$(($COUNT -1))
# $time_stamp is the date of snapshots
time_stamp=`date "+%F_%H-%M"`
# Clean up older snapshots:
for i in `ls $TARGET|sort |grep ${SNAP}|head -n -${max_snap}`; do
cmd="btrfs subvolume delete $TARGET/$i"
if [ -z $QUIET ]; then
echo $cmd
fi
$cmd >/dev/null
done
# Create new snapshot:
cmd="btrfs subvolume snapshot $SOURCE $TARGET/"${SNAP}-$time_stamp""
if [ -z $QUIET ]; then
echo $cmd
fi
$cmd >/dev/null
I use fcontab
[root@kabuky ~]# fcrontab -l
17:32:58 listing root's fcrontab
@ 5 /usr/local/bin/btrfs-snapshot /home /home/__snapshots minutely 60 -q
@ 1h /usr/local/bin/btrfs-snapshot /home /home/__snapshots hourly 48 -q
@ 1d /usr/local/bin/btrfs-snapshot /home /home/__snapshots daily 28 -q
@ 1w /usr/local/bin/btrfs-snapshot /home /home/__snapshots weekly 16 -q
@ 1m /usr/local/bin/btrfs-snapshot /home /home/__snapshots monthly 12 -q
And this is what i get
[root@kabuky ~]# ls /home/__snapshots
[root@kabuky ~]# ls -l /home/__snapshots
total 0
drwxr-xr-x 1 root root 30 Jul 15 19:00 hourly-2011-10-31_17-00
drwxr-xr-x 1 root root 30 Jul 15 19:00 hourly-2011-10-31_17-44
drwxr-xr-x 1 root root 30 Jul 15 19:00 minutely-2011-10-31_17-18
drwxr-xr-x 1 root root 30 Jul 15 19:00 minutely-2011-10-31_17-20
drwxr-xr-x 1 root root 30 Jul 15 19:00 minutely-2011-10-31_17-22
drwxr-xr-x 1 root root 30 Jul 15 19:00 minutely-2011-10-31_17-24
drwxr-xr-x 1 root root 30 Jul 15 19:00 minutely-2011-10-31_17-26
drwxr-xr-x 1 root root 30 Jul 15 19:00 minutely-2011-10-31_17-32
drwxr-xr-x 1 root root 30 Jul 15 19:00 minutely-2011-10-31_17-37
drwxr-xr-x 1 root root 30 Jul 15 19:00 minutely-2011-10-31_17-42

tavianator wrote:
Cool, I just wasn't sure if the "And this is what i get" was what you were expecting.
Looks good, I may take a look since I'm using btrfs.  Don't confuse this for a backup though .
Sorry for confusion, my english is not very good
Yes this is not a backup.
It's a sort of parachute if you do something stupid with your files you can at any time come back

Similar Messages

  • Trying to understand BtrFS snapshot feature

    I'm trying to understand how the copy-on-write and Btrfs snapshot works.
    Following simple test:
    <pre>
    # cd /
    # touch testfile
    # ls --full-time testfile
    -rw-r--r-- 1 root root 0 2012-10-15 12:04:43.629620401 +0200 testfile
    Test 1:
    # btrfs subvol snapshot / /snap1
    # touch testfile
    # ls --full-time testfile /snap1/testfile
    -rw-r--r-- 1 root root 0 2012-10-15 12:04:43.629620401 +0200 /snap1/testfile
    -rw-r--r-- 1 root root 0 2012-10-15 12:07:38.348932127 +0200 testfile
    Test 2::
    # btrfs subvol snapshot / /snap2
    # touch testfile
    # ls --full-time testfile /snap1/testfile /snap2/testfile
    -rw-r--r-- 1 root root 0 2012-10-15 12:04:43.629620401 +0200 /snap1/testfile
    -rw-r--r-- 1 root root 0 2012-10-15 12:07:38.348932127 +0200 /snap2/testfile
    -rw-r--r-- 1 root root 0 2012-10-15 12:09:21.769606369 +0200 testfile
    </pre>
    According to the above tests I'm concluding/questioning the following:
    1) Btrfs determines which snapshot maintains a logical copy and physically copies the file to the appropriate snapshot before it is modified.
    a) Does it copy the complete file or work on the block level?
    b) What happens if the file is very large, e.g. 100 GB and there is not enough space on disk to copy the file to the snapshot directory?
    c) Doesn't it have a huge negative impact on performance when a file needs to be copied before it can be altered?

    Hi, thanks for the answers!
    I guess calling it "logical copy" was a bad choice. Would calling the initial snapshot a "hard link of a file system" be more appropriate?
    Ok, so BTRFS works on the block level. I've done some tests and can confirm what you said (see below)
    I find it interesting that although the snapshot maintains the "hard link" to the original copy - I guess "before block image" (?) - there really is no negative performance impact.
    How does this work? Perhaps it is not overwriting the existing file, but rather creating a new file? So the snapshot still has the "hard link" to the original file, hence nothing changed for the snapshot? Simply a new file was created, and that's showing in the current file system?
    It actually reminds me of the old VMS ODS filesystem, which used file versioning by adding a simicolon, e.g. text.txt;1. When modifying the file the result would be text.txt;2 and so on. When listing or using the file without versions, it would simply show and use the last version. You could purge old version if necessary. The file system was actually structured by records (RMS), similar like a database.
    <pre>
    [root@vm004 /]# # df -h /
    Filesystem Size Used Avail Use% Mounted on
    /dev/sda3 16G 2.3G 12G 17% /
    # time dd if=/dev/zero of=/testfile bs=8k count=1M
    1048576+0 records in
    1048576+0 records out
    8589934592 bytes (8.6 GB) copied, 45.3253 s, 190 MB/s
    Let's create a snapshot and overwrite the testfile
    # btrfs subvolume snapshot / /snap1
    # time dd if=/dev/zero of=/testfile bs=8k count=1M
    dd: writing `/testfile': No space left on device
    491105+0 records in
    491104+0 records out
    4023123968 bytes (4.0 GB) copied, 21.2399 s, 189 MB/s
    real     0m21.613s
    user     0m0.021s
    sys     0m3.325s
    <pre>
    So obviously the there is not enough space to maintain the original file and the snapshot file.
    Since I'm creating a complete new file, I guess that's to be expected.
    Let's try with a smaller file, and also check performance:
    <pre>
    # btrfs subvol delete /snap1
    Delete subvolume '//snap1'
    # time dd if=/dev/zero of=/testfile bs=8k count=500k
    512000+0 records in
    512000+0 records out
    4194304000 bytes (4.2 GB) copied, 21.7176 s, 193 MB/s
    real     0m21.726s
    user     0m0.024s
    sys     0m2.977s
    # time echo "This is a test to test the test" >> /testfile
    real     0m0.000s
    user     0m0.000s
    sys     0m0.000s
    # btrfs subvol snapshot / /snap1
    Create a snapshot of '/' in '//snap1'
    # df -k /
    Filesystem 1K-blocks Used Available Use% Mounted on
    /dev/sda3 16611328 6505736 8221432 45% /
    # time echo "This is a test to test the test" >> /testfile
    real     0m0.000s
    user     0m0.000s
    sys     0m0.000s
    # df -k /
    Filesystem 1K-blocks Used Available Use% Mounted on
    /dev/sda3 16611328 6505780 8221428 45% /
    # btrfs subvol delete /snap1
    Delete subvolume '//snap1'
    # df -k /
    Filesystem 1K-blocks Used Available Use% Mounted on
    /dev/sda3 16611328 6505740 8221428 45% /
    The snapshot occupied 40k
    # btrfs subvol snapshot / /snap1
    Create a snapshot of '/' in '//snap1'
    # time dd if=/dev/zero of=/testfile bs=8k count=500k
    512000+0 records in
    512000+0 records out
    4194304000 bytes (4.2 GB) copied, 21.3818 s, 196 MB/s
    real     0m21.754s
    user     0m0.019s
    sys     0m3.322s
    # df -k /
    Filesystem 1K-blocks Used Available Use% Mounted on
    /dev/sda3 16611328 10612756 4125428 73% /
    There was no performance impact, although the space occupied doubled.
    </pre>

  • Tnventory Management Weekly snapshot 0IC_C03

    Hi,
    We are trying to instal the stocks Flow, with the 0IC_C03 cube. Our Business Content (Release 703 Level 8) has the new Infosources (2LIS_03_BF_TR, 2LIS_03_BX_TR and 2LIS_03_UM_TR) and the related transformations from the Infosources to the cube. But We've realized taht there is not one of the Transformations from 2LIS_03_BF datasource to 2LIS_03_BF_TR infosource. (The othrer 2 transformations appear in our Business Content)
    We are thinking to do the following: mantain the transformations for the 2LIS_03_BX and 2LIS_03_UM side, and copy from another business Content (manually, of course) the 2LIS_03_BF side. Has anybody know if it is OK?
    On the other hand, we need to create a Weekly snapshot, and reviewing the document "How to... handle Inventory Management Scenarios in BW", there is described the process to make a monthly snapshot if the old flow of the 3 datasources (2LIS_03_BF, 2LIS_03_BX and 2LIS_03_UM) is built (the flow with the Transfer and Update Rules)
    So, is it recomended to implement the old flow for the 3 datasources (the one with Transfer and Update Rules)? And does anybody knows how can we modify the routines in order to make it weekly, not monthly?
    Thanks in advance for your help.
    Best regards

    Hello Angel Moro,
    Were you able to implement weekly snapshot cube? If yes, Can you please email me step by step how you did it at [email protected]

  • Inventory management with SnapShots

    Hi
    I've got this document, "How to handle inventory management scenarios in BW".
    It's generally very clear, no problem to understand the standard solution (0IC_C03, non-cumulatives).
    But I really didn't understand the explanation about Snapshot on the monthly positions.
    So I ask someone to explain how does the concept work.
    Example:
    The document refers to material movements in 01.2004 and 03.2004.
    Question 1:
    What are the values posted to the DSO and to the InfoCube after initial load (after the first load of datasources BX and BF/UM) ???
    Will we have registers to 01.2004, 02.2004, 03.2004 and 12.9999, both in the DSO and in the InfoCube ?
    How does month 12.9999 work?
    Question 2:
    What are the values posted to the DSO and to the InfoCube after the second BF load?
    Let's suppose 2 movements in 04.2004 and 2 movements in 05.2004.
    Will we add registers to 04.2004 and 05.2004 both in the DSO and in the Cube?
    Thanks in advance.
    Cesar Menezes

    Hi Cesar,
    Not sure if this could be helpful.. but still sharing..
    http://www.biportal.org/discussion_forum?mode=MessageList&eid=350671
    As even I want to understand differences between 2 methods.. Snapshot and 0IC_C03 (non cumulative)
    Could you find any leads?
    Regards, Vittali

  • Inventory Management, New Snapshot Scenario

    We are planning to implement the New Snapshot scenario for Inventory Management. This is based on the "How to...." document. As per what is shown in the document, all the 3 extractors feed into the same DSO. However, when I try to create the Update Rules for <b>BX</b>, I get a error that there is no key figure. However, the DSO (Standard) has the Key figures. These are cummulative. Maybe, because of that I get the error when I create update rules for BX. But then, in the document the key figures appear. How is this possible.
    Has anyone tried this and has been successful. If so, I'd appreciate if you could send some tips.
    Thanks

    hello
    can you please take a screenshot of your data model and update rules (inside) and send me to (see email in card)
    It will really help me!
    Alex

  • How to create a btrfs snapshot from the actual state?

    Hi all,
    i would like to create a backup via a snapshot from my root volume. How can i create a snapshot from the actual state of my partition and mount it again?
    best regards :>

    Long time ago but it could be usefull for someone else.
    Create snapshot of whole disk on btrfs:
    $sudo btrfsctl -s /mnt/snapshot/`date +%F` /
    Delete snapshot (don't try to delete it with "btrfsctl -D", it won't work yet):
    $sudo btrfs subvolume delete /mnt/snapshot/2011-06-19/
    Also usefull could be to create subvolumes for snapshoting. This create testvolume directory with subvolume in /mnt.
    $sudo btrfsctl -S testvolume /mnt/
    Last edited by fraantik (2011-06-19 14:52:54)

  • Anyone ever have issues with btrfs snapshots?

    So my arch system was installed on btrfs as recommended with root as a subvolume. I kept it simple and only had one root subvolume (nothing seperate for /home and the like).
    I have taken a few snapshots by mounting the btrfs root (subvolid=0) and then running this simple command "btrfs subvolume snapshot archroot archroot_snapshot_`date +%F`".
    Now today, I deleted a lot of stuff on my arch install such as /var and /home and completely messed it up so it would not boot. Then in recovery I set one of the snapshots to be default and made sure the kernel boot lines in grub used that snapshot subvolume. Booted into it and to my surprise it had many failed services on boot. The snapshot should have been a working snapshot. I found that /var was now empty and upon checking all the other snapshots which were not even touched, they all had an empty /var as well.
    Does anyone know what I did wrong and why /var was apparently erased in all snapshots when I removed it in the original? My understanding was that snapshots should not be effected by any other snapshots.
    Last edited by xamindar (2015-02-17 19:28:54)

    Spider.007 wrote:It seems like /var was either on another partition; or was actually a subvolume itself. Since snapshots are 'non-recursive' (they don't snapshot other subvolumes that you mounted) it would explain your issue. The fact that 'subvoilume list' lists the snapshots is obvious, but are you sure it didn't list other subvolume (such as /var) as well?
    So if I had the root subvolume as "archroot" and another subvolume under that as "archroot/var", this would explain my issue. Any snapshotting of "archroot" would not include the var subvolume under the archroot subvolume. Did I understand that right?
    That is a possibility. It was my first time using btrfs and any snapshotting type filesystem so it is possible I may have created another subvolume for var in my testing.
    Thanks for the explanation.

  • Inventory management: non-cumulatives VS. snapshots

    In the How to <i>Handle Inventory Management Scenarios in BW</i>, I read that (p. 2):
    - Inventory management with non-cumulative key figures is better when <i>"90 percent of all materials were moved 1 time in the month"</i>;
    - Inventory management with SnapShots is better when <i>"90 percent of all materials were moved 1 time in the month"</i>.
    I think the second sentence is not correct. But what can be the right number of movements to be considered?
    Thanks a lot,
    Davide

    Hi Ajay,
    so my next question is:
    Besides the time granularity needed (daily-level vs. monthly-level), is there a threshold for the number of movements, that could be used to choose one of the two models?
    I mean, if materials are moved on average e.g. less than 10 times per month, the non-cumulative architecture could be best one. While if there are more than 10 times per month, the snapshot architecture could be more appealing. In this example, 10 movements per month is the threshold.
    Cheers, Davide

  • Problems Implementing SnapShots Scenario for Stock Management

    Hello All,
    I am trying to configure the Inventory Management with snapshots and I am using the snapshot scenario. According to the document I have created alternative ODS ODSSNAP and infocubes to accumulate 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM.
    My problem is with the key figures ZTOTALST,ZVALSTCKV and ZVALSTCKQ.
    I am facing this problem in the ODS when i try to create the update rule for 2LIS_03_BX. I have the two Characteristics Unit and Currency automatically mapped but i don´t see the key figures of the ODS. I supposed that my key figures may appear without assignment but they don´t appear.
    I should have my key figures non mapped but instead I cannot see them.I tried with another standard infosource 2LIS_03_BF and I see my key figures.
    I have BW 3.5 patch level 20.
    Can you please let me know any ideas?
    Thanks
    TK

    OK, non cumulative are not stored in your provider but calculated on the fly:
    NonCum = InFlow - OutFlow.
    then you have to work with your good receipts and goods issue flow key figures....
    For your scenario, as far as I understood you just need to see a "snapshot" (latest know stock values) you just need to update your receipts and issues with summation in your ODS; your stock will then be calculated.
    Usually a "snapshot" scenario means that you want to store your stock at the end of each month for example; in this case you need to use cumulatives with exception aggregation "LAST" on your time period so that the stocks aren't summarized over time. This way you update your cumulative Stk KF is updated with goods receipts - good issues. Also remind that in this scenario you'll have to load the previous month stock into the next
    Stock July = Stock June + Receipts July - Issues July.
    As you realize, it can get quite complex...
    Please precise your requirement and we'll help you further since I am doing all kind of scenario re stocks...
    hope this helps...
    Olivier.

  • BTRFS mkinitcpio hook

    UPDATE (6/10/10): http://bbs.archlinux.org/viewtopic.php? … 51#p772651
    THIS POST DEPRECATED UNTIL I UPDATE IT, USE THE UPDATED POST ABOVE
    available:
    http://aur.archlinux.org/packages.php?ID=33376
    this package will install a mkinitcpio hook intended for those who wish to have a single or multi-drive BTRFS file system as their / (root).  the hook will ensure that the chosen root device from the kernel command line is intact and safe to boot.  if root is not a BTRFS device, the hook is quietly skipped.
    it requires btrfs-progs from here:
    http://aur.archlinux.org/packages.php?ID=15635
    hook supports both UUID or device based root names.  UUID is safer; the entire BTRFS array only has one UUID, so referring to it means no problems. use /dev/device/by-uuid on kernel boot.
    hook supports hot spares by using a dummy, spare BTRFS file system to steal devices from as needed.  the spare pool can be referenced by label or UUID.**
    hook supports automatic repairing of the array if possible, automatic dropping of missing/failed devices if possible, and booting the array to a degraded state (one or more devices missing) if possible.**
    **NOTE: there are some bugs that may be in the hook/btrfs module/btrfs-progs that prevent raid1 (maybe others) arrays from being repaired (see http://pastebin.com/m5706f47f) however, this hook will work fine as is for single/multi-device arrays that are intact.  enable experimental options manually by editing options in the hook itself (/lib/initcpio/hooks/btrfs).  USE WITH CAUTION ON MULTI-DEVICE SETUPS.
    the initramfs script can be seen here:
    http://aur.archlinux.org/packages/mkini … btrfs_hook
    its fairly commented, although there are a few things i'll point out for others who want to edit:
    1) i plan to rework _btrfs_scandev() to be more flexible in the variables it produces.  that function simply parses "btrfs-show" and gleans valuable information from it.  it will be used to verify array states with certainty.
    2) seems that btrfsctl does not have meaningful exit codes right now, do not rely, see _btrfs_register().
    3) seems that after legitimately removing a device from an array (NOT using "missing" special keyword), the mount needs a "mount -o remout [mnt]" for the ***missing flag to be removed from btrfs-show.  not sure the ramification of this or if its necessary.
    4) some or all of this functionality may someday be provided by module/kernel
    needs work + comments
    add "btrfs" to HOOKS in mkinitcpio.conf
    Last edited by extofme (2010-06-10 06:09:10)

    bleh, sorry about the late response, i usually subscribe to topics i create/join, i must have missed this one.
    resi wrote:After minor problems with the mkinitcpio (lvm hook seems to conflict with the btrfs one) image and fstab (why do I have to specify the root fs there? its already mounted when fstab is examined)
    i could be mistaken here, but initially your / is mounted read-only.  during the init process, one of the primary scripts issues a "mount -o remount,rw /" to remount the root device as read-write.  i _think_ using the mount command in this way (against a mount point and not a device) requires the mount point to exist in the fstab.
    resi wrote:But what happens if I really screw it up? I'm on 2.6.33 (.2-1) and read about missing ioctl()s regarding btrfs, meaning I can't replace the "default" subvolume (whats the difference between a subvolume and a snapshot anyway?). Its also not possible to list available subvolumes/snpshots, meaning your script (or organizing snapshots in similar ways) is the only chance to keep track of them, right?
    the inability to set the default subvolume is kind of a non-issue after i thought about it more, and some of the discussion on arch-general.  i plan to update the hook soon to allow the "promotion" of the rollback to become the new active subvolume.  ill do this by snapshotting your current / to a new subvolume called /__active, and then permanently booting into that [__active] instead of / or "." (a period is the default subvolume, like current directory).
    there is no difference internally, whatsoever (AFIAK), between a subvolume and a snapshot.  its just a matter of context: a subvolume starts out empty (explicitly created via a command/etc.), and a snapshot starts out with content (COW operation against an existing subvolume, i.e. "copy")
    yeah without the ability to list available subvolumes, we have to make up some structure, and assume everything goes well.  my script simply assumes anything within /snapshots is indeed a snapshot that can be copied (to /__rollback) and booted.  even if we can list subvolumes, we'll still need some kind of predefined structure (so the script knows which snapshots are bootable, and which are not, i.e. snapshots of /home are not bootable).
    resi wrote:I guess a plain "mount -t btrfs /dev/xyz" will mount the "default" subvolume then.
    correct.
    resi wrote:
    Once I really screw up I will have to boot into a snapshot, mount the default subvolume somewhere and restore it using a full copy from the snapshot (a la rsync --delete), then reboot and I'm back at the start again.
    Is this correct?
    unfortunately, without modifying the script, a manual copy is necessary :-( totally defeating the advantages of btrfs.  so, yes.  the problem is that the default subvolume itself cannot be replace by another... note this is different from SETTING the default subvolume.  i'm not sure if the real default subvolume ("." the period) will ever be replaceable/removable, i'd have to ask the btrfs list.  this is why i advocate installing your system into a subvolume FROM THE BEGINNING.  this gives us more flexibility.
    resi wrote:Is there some way to permanently change the subvolume mounted by your hook (i.e. not running in a volatile snapshot, but actually drop the default one and always boot into a given snapshot until further notice - a new snapshot)?
    this is actually how i intend to implement non-volatile rollback abilities in the hook.  instead of booting the default "." subvolume, my hook will ALWAYS boot the subvolume called "__active", located at /__active.  this way you can put whatever you want there, and it will be booted at the next reboot.  therefore, you can boot into rollback mode (essentially booting into /__rollback), update/add/remove whatever you want, and when your satisfied, you simply snapshot /__rollback to /__active and your done.  reboot, and your new __active will be in the same state as the point it was created in rollback mode.
    does all this make sense?  i'm told i tend to over explain/complicate things :-).
    resi wrote:Before every -Syu I have to check for kernel/xorg updates, read about them, check the mailing list, wait ... wait ... wait ... loose patience, give it a shot, recompile/reinstall the necessary stuff (at least I've got PKGBUILDs prepared) and hope for the best. With btrfs, this is just a non-issue. Or at least will be once the integration is better.
    i hear ya.  i like the idea of riding the edge without the fear of being cut by it.  unfortunately, until btrfs is supported by grub2, kernel rollbacks aren't possible (you'd have to manually backup your old kernel+initrd).  something to keep in mind.
    hunterthomson wrote:However, if I can just tell my clients to reboot into a snapshot "problem solved." Then I can spend the time to solve the problem, without the client siting around with a broken system.
    bingo.  that is pretty much my primary motivation here... less time freaking out about down time/whatever; everybody wins.
    hunterthomson wrote:Did you know Fedora 13 supports Btrfs Snapshotting and Roll-Back. Super cool.
    i know they have some support but i haven't tried it; from what i've read, the support is pretty weak... you can get yum to create the snapshot by installing a package, but there is no utility to actually use them later on.  i could be mistaken as i don't use fedora, this is only what i've read.
    what sucks is pacman doesnt have any ability to use hooks... i dont think we will see automatic snapshots by the package manager without a wrapper like clyde/powerpill/packer/etc.
    C Anthony

  • How to handle inventory management scenario

    Hi All,
    In How to handle inventory management scenario whitepaper, I fail to understand the basic difference between 'Inventory Management with non-cumulative Key Figures' and 'Inventory Management with Snapshots'. Can anyone please explain me the basic difference.
    Thanks
    PB

    Hi Loic
    Can u please see if all the steps listed below are OK.
    While setting up  the IM Scenario
    I have jotted down the steps with valuable inputs from you  and paper 'How to Hanlde IM scenarios'
    Please find the steps below. Kindly review them and let me know in case I have got anything wrong or missed out on anything.
    1. Transfer Business Content Datasources 2LIS_03_BX , 2LIS_03_BF, AND 2LIS_03_UM in RSA5.
    2. Go to Transaction LBWE, Activate Datasources 2LIS_03_BF, AND 2LIS_03_UM.
    3. Go to Transaction MCB_ select SAP BW usage 'Standard' Radio button.
    4. Save it.
    5. Go to Transaction MCNB, enter name of run ‘Stock_init’. Enter Termination date in future. Enter Datasource as 2LIS_03_BX.
    6. Execute the initialisation.
    7. Entries can be found in SETUP Table MC03BFSETUP & MC03BFSETUP.
    8. Run SETUP for 2LIS_03_BF, AND 2LIS_03_UM using TCodes OLI1BW and OLIZBW respectively.
    9. Run the extraction for 2LIS_03_BX in BW.
    10. Compress the request with ‘No Marker Update’ NOT SET i.e. unticked or unchecked.
    11. Run the extraction for 2LIS_03_BF in BW.
    12. Compress the request with ‘No Marker Update’ SET i.e. ticked or checked.
    13. Run the extraction for 2LIS_03_UM in BW.
    14. Compress the request with ‘No Marker Update’ SET i.e. ticked or checked.
    Steps 1 and 2 shall be executed in Development and transported to production and step 3 onward should be carried out in Production itself with Posting Block.
    Thanks in advance.
    Regards
    PB

  • (V8.1 REPLICATION) UPDATABLE SNAPSHOT환경 구축을 위한 초기 작업

    제품 : ORACLE SERVER
    작성날짜 : 2001-07-19
    (V8.1 REPLICATION) UPDATABLE SNAPSHOT환경 구축을 위한 초기 작업
    =============================================================
    1. 개요
    =======
    Symmetric Replication의 한 종류인 updatable snapshot환경의 구축을 위해서는
    replication manager를 사용하도록 한다. 이 문서는 replication manager사용을
    통해 snapshot group및 object 등을 등록하고 관리하기 이전에 master및 snapshot
    site에서 미리 설정되고 수행되어야 하는 작업들을 정리한다.
    이중 일부 작업은 replication manager를 통해서도 구현이 되지만, 정확한
    수행이 요구되어 지는 작업에 대해서는 이 문서에서와 같이 직접 SQL command를
    통해 수행되어지는 것이 권고된다.
    Oracle 8.1.x부터는 snapshot과 materialized view가 동의로 사용되어지나, 이
    문서에는 snapshot으로 표시한다.
    2. Init.ora parameters
    ======================
    아래와 같은 initialisation parameter들이 추가되거나 수정되어져야 한다.
    아래의 설정은 master site와 snapshot site모두 설정이 필요하며, master site가
    하나뿐인 경우는 job_queue부분과 parallel_ parameter의 경우는 설장할 필요가
    없다.
    Parameter 이름 권장되는 초기 값
    COMPATIBLE 8.1.5.0.0 이상
    SHARED_POOL_SIZE 20M ~ 40M 정도가 추가로 요구
    PROCESSES 현재 값에서 12정도 추가
    GLOBAL_NAMES 반드시 TRUE
    OPEN_LINKS 4, 추가되는 master site당 2 증가
    DISTRIBUTED_TRANSACTIONS 최소 5 이상 (기본값은 trsactions/4)
    가되는 master site당 2 증가
    REPLICATION_DEPENDENCY_TRACKING TRUE
    아래의 값은 상황에 맞게 조정하여 사용한다.
    JOB_QUEUE_INTERVAL 10 초
    JOB_QUEUE_PROCESSES 3, 추가되는 master site당 1씩 증가
    PARALLEL_MAX_SERVERS 10
    PARALLEL_MIN_SERVERS 2, max server의 갯수와 동일한것이 권장
    parallel propagation을 사용하지 않고자
    하면 설정하지 않는다.
    SNAPSHOT_ 로 시작하는 parameter나 JOB_QUEUE_KEEP_CONNECTIONS parameter는
    Oracle 8.1에서는 없어졌으므로 지정하지 않도록 한다.
    3. Tablespace 요구 사항
    =======================
    다음은 replication을 사용하기 위해 추가적으로 필요한 tablespace용량이다.
    Tablespace 권장사항
    SYSTEM 최소 40 Mb free space
    ROLLBACK SEGMENTS 최소 30 Mb free space
    TEMPORARY 최소 20 Mb free space
    4. Replication Catalogue 설치
    ==============================
    database생성시에 replication catalog를 설치하지 않았다면, Database
    Configuration Assistant 를 이용하여 Advance Replication Option부분을
    database에 추가하도록 하거나, 아니면 다음과 같이 작업한다.
    cd $ORACLE_HOME/rdbms/admin
    sqlplus internal
    SQL>spool rep.log
    SQL>@catrep
    SQL>spool off
    이 script는 약 1시간 정도 수행되며, spool을 받아 수행에 문제가 있었는지
    이후에 확인하도록 한다.
    [주의] 이 script를 수행하게 되면, replication관련 table과 queue등이 system
    owner로 생성되게 된다.
    그러므로 이후에 replication작업이 일시 중단되어 queue가 커지게 되면,
    system user의 default tablespace에 부담이 되므로 system owner의
    default tablespace를 tools나 그외 replication관리를 위한 별도의
    table로 일시 지정하도록 한다.
    SQL>ALTER USER sysem DEFAULT TABLESPACE REPTBS;
    catrep의 수행이 끝나면 spool로 생긴 rep.log도 확인하여 보고, 아래 문장을
    통해 invalid상태인 object를 확인하고 재 compile을 시도한다.
    SQL> SELECT OWNER, OBJECT_NAME FROM ALL_OBJECTS
    WHERE STATUS = 'INVALID';
    이때 만약 SYS나 SYSTEM package의 body가 invalid로 나타나면 다음과 같이 재
    compile을 시도한다. package body만 invalid인데 aler package문장에서 compile
    body대신 compile이라고만 하면 그 package에 대한 definition이 변경되어,
    이 package와 dependency관계에 있는 다른 object도 invalid상태가 되도록 한다.
    작업이 성공적으로 끝났으면, system user의 default tablespace의 원래대로,
    tool나 system으로 수정한다.
    SQL> alter user system default tablespace system;
    5. Setup NET8
    =============
    Replication환경에 포함된 모든 server는 listener를 구동하도록 하며, snapshot
    site에서는 master site를 가리키는 service alias를 tnsnames.ora file에 등록하
    도록 한다.
    또한, replication manager를 사용하는 client도 tnsnames.ora file에 master와
    snapshot site와 연결가능하도록 service alias를 net8 easy configuration등을
    통하여 등록하도록 한다.
    6. Replication Manager Setup Wizard
    ===================================
    위의 작업이 모두 끝났으면 앞으로의 작업은 replication manager를 통해서도
    수행 가능하다.
    그러나 이 문서에 포함된 내용은 replication환경 설정시 한번만 필요한 작업이며,
    이 부분에 대한 사소한 실수도 이후 사용에 문제를 야기하기 때문에, 여기에 포함된
    작업만큼은 sql command를 통해 직접 작업하기를 권고한다.
    Replication manager가 포함되어 있는 OEM version은 1.4부터이며, Oracle8.1의
    경우는 2.1이 최적화되어 있다. 그러나 그 이전 version도 사용가능하다.
    7. Replication Users
    =====================
    일반적으로, multi-master환경보다는 updatable snapshot환경이 더 보안이 문제시
    된다. multi-master의 경우는 일반적으로 중앙에서 같은 db admin에 의해 관리
    되는것이 일반적이나 snapshot의 경우는 지역적으로 떨어져 별개로 관리되는 경우가
    많아 그 snapshot에서 master site의 database에 손상을 주는 일을 막는것이
    중요하여, user구성은 multi-master환경보다 복잡하다.
    Snapshot Site Master Site
    Replication administrator
    Snapshot replication administrator ---> Proxy snapshot administrator
    Propagator ---> Receiver
    Refresher ---> Proxy refresher
    Snapshot Owner(s) ---> Proxy refresher
    - Replication administrator: master site에서, master group들의 구성과
    관리를 책임진다.
    - Snapshot administrators: snapshot site에서 snapshot replication group을
    구성하고 관리하는 책임을 지며, master site의 Proxy administrator가
    master group의 최소한의 access만 허용하게 된다.
    - Propagators: deferred transaction을 master site에 전달하면, master site의
    Receiver가 전달받은 data를 master table에 적용시킨다.
    - Refreshers: snapshot site에서 master site의 변경된 data를 snapshot
    site로 끌어오는 역할을 하며, master site의 Proxy refresher는 master
    site의 table에 대한 최소한의 acess만을 허용한다.
    이러한 user들의 생성하고 이용하는 방법은 여러가지로 가능하다. 아래에서는,
    그중 가장 일반적으로 사용되는 방법을 기술한다.
    8. Replication user 생성 및 권한 부여
    =====================================
    Oracle 8.1부터 updatable snapshot 환경 구축시 trusted와 untrusted두가지
    방법이 가능하다. untrusted의 경우 snapshot site가 master site와 같은 관리자
    아래에 포함되지 않아 보안을 더 강화해야 하는 model이다.
    하나의 master site에 snapshot group이 여러개이고, 각 snapshot별로, 이
    snapshot group을 공유하는것이 아니고, 별개로 사용하는 경우 서로 다른
    snapshot이 사용하는 group에 대해 보안을 유지하려면 untrusted model을 사용해야
    하나 실제 이러한 환경으로 구성되는 일은 거의 없고, 작업의 번거로움으로 이
    문서에는 trusted model에 대해서는 설명한다.
    8.1 Master Site user와 권한
    (1) Replication Administrator (REPADMIN)
    SQL>CONNECT system/<password>
    SQL>CREATE USER repadmin IDENTIFIED BY <password>
    DEFAULT TABLESPACE <tablespace name>
    TEMPORARY TABLESPACE <tablespace name>;
    SQL>GRANT connect, resource TO repadmin;
    SQL>EXECUTE dbms_repcat_admin.grant_admin_any_schema('repadmin');
    SQL>GRANT comment any table TO repadmin;
    SQL>GRANT lock any table TO repadmin;
    만약 replication group이 어느 특정 schema에만 한정된다면,
    grant_admin_any_schema대신 grant_admin_schema를 사용하여도 된다.
    (2) Proxy snapshot administrator / Receiver / Proxy refresher (SNAPPROXY)
    master site의 proxy snapshot administrator, receiver, proxy refresher는
    하나의 user로 관리하는 것이 일반적이다. 이러한 SNAPPROXY user를 생성하지
    않고 REPADMIN user가 이러한 역할도 수행하도록 설정할 수 있으나, 그렇게
    되면 snapshot site에 너무 많은 권한을 부여하게 되어 바람직하지 않다.
    replication manager를 이용해 이러한 user를 생성하면 master site에 연결된
    snapshot site마다 각각의 snapproxy_n과 같은 형태로 user를 생성하나,
    같은 snapshot group에 대하여 이렇게 각각의 user를 생성하는 것은 의미가
    없으므로 권장되지 않는다.
    SQL>CONNECT system/<password>
    SQL>CREATE USER snapproxy IDENTIFIED BY <password>
    DEFAULT TABLESPACE <tablespace name>
    TEMPORARY TABLESPACE <tablespace name>;
    (3) Proxy snapshot administrator privileges
    SQL>CONNECT system/<password>
    SQL>BEGIN
    dbms_repcat_admin.register_user_repgroup(
    username => 'snapproxy',
    privilege_type => 'proxy_snapadmin',
    list_of_gnames => NULL);
    SQL>END;
    SQL>/
    register_user_repgroup procedure를 통해 권한을 부여한다. 이때, "create
    session" 과 dbmsobjgwrapper / dbms_repcat_untrusted package에 대한
    "execute"권한이 부여된다.
    Replication group에 table을 add하게 되면 그 table에 대한 "select" 권한이
    부여된, master objects에 대한 DML권한은 이 user에게 부여되지 않는다.
    (4) Receiver privileges
    SQL>CONNECT system/<password>
    SQL>BEGIN
    dbms_repcat_admin.register_user_repgroup(
    username => 'snapproxy',
    privilege_type => 'receiver',
    list_of_gnames => NULL);
    SQL>END;
    SQL>/
    이 문장을 통해 "create session" 과 dbms_defer_internal packages,
    dbms_defer package에 대한 "execute"권한이 부여된다. 그러나 이것도
    마찬가지로 master object에 대한 DML권한을 부여하지 않는다.
    또한 receiver는 replication object를 추가한 후 replication support시에
    생성되는 <schema>.<object name>$RP (LOB table에 대해서는 $RL)에 대한
    execute권한을 부여 받아 master site에 변경사항을 적용하게 된다.
    (5) Proxy refresher privileges
    SQL>CONNECT system/<password>
    SQL>GRANT create session TO snapproxy;
    SQL>GRANT select any table TO snapproxy;
    (6) Schema Owner(s) (여기에서는 REPUSER로 명시)
    SQL>CONNECT system/<password>
    SQL>CREATE USER repuser IDENTIFIED BY <password>
    DEFAULT TABLESPACE <tablespace name>
    TEMPORARY TABLESPACE <tablespace name>;
    SQL>GRANT connect, resource TO repuser;
    8.2 Snapshot Site user와 권한
    (1) Snapshot administrator / Propagator / Refresher (SNAPADMIN)
    snapshot administrator, propagator, refresher에 대해서 하나의 user로
    관리하는것이 일반적이다.
    SQL>CONNECT system/<password>
    SQL>CREATE USER snapadmin IDENTIFIED BY <password>;
    DEFAULT TABLESPACE <tablespace name>
    TEMPORARY TABLESPACE <tablespace name>;
    (2) Snapshot administrator 권한
    SQL>CONNECT system/<password>
    SQL>EXECUTE dbms_repcat_admin.grant_admin_any_schema('snapadmin');
    SQL>GRANT comment any table TO snapadmin;
    SQL>GRANT lock any table TO snapadmin;
    (3) Propagator 권한
    SQL>EXECUTE DBMS_DEFER_SYS.REGISTER_PROPAGATOR('snapadmin');
    (4) Refresher 권한
    SQL>GRANT create any snapshot TO snapadmin;
    SQL>GRANT alter any snapshot TO snapadmin;
    refresher와 대응하는 master site의 proxy refrsher에 의해 master site의
    table에 대한 "select any table" 권한을 가지게 된다.
    (5) Schema Owner(s) (여기에서는 REPUSER로 명시)
    replicate되고자 하는 table에 대한 master site의 schema와 동일한 이름의
    shema가 snapshot site에서도 필요하다. 단 password는 같을 필요는 없다.
    만약 다른 schema에 대해서 updatable snapshot을 생성하면, snapshot생성시는
    오류없이 만들어지지만, create_snapshot_repobject 수행시에 아래와 같이
    오류가 발생할 것이다.
    ORA-23306: schema <schema name> does not exist
    ORA-23308: object <schema name>.<object name> does not exist or is invalid
    아래 문장과 같은 schema owner생성시 주의할 점은 이 권한을 role을 통해
    부여하지 말고 직접 주어야 한다는것이다. 즉, 이미 connect, resource등을
    통해 create table과 같은 권한은 부여된 상황임에도 불구하고, 이후에
    procedure나 package등에서 이 권한이 필요한 경우 role을 통해 부여된 것은
    인식이 되지 않고 ORA-1031이 발생하기 때문에 아래와 같이 직접 권한을
    부여하여야 한다.
    SQL>CONNECT system/<password>
    SQL>CREATE USER repuser IDENTIFIED BY <password>
    DEFAULT TABLESPACE <tablespace name>
    TEMPORARY TABLESPACE <tablespace name>;
    SQL>GRANT connect, resource TO repuser;
    SQL>GRANT create table TO repuser;
    SQL>GRANT create snapshot TO repuser;
    이 user가 master site에 대해서 수행할 수 있는 권한에 대해서는 이 user에서
    master site로 생성하는 database link를 어느 user로 connect하느냐에 달려
    있으며 이것은 9.4에서 설명한다.
    (6) End Users
    snapshot schema에 있는 snapshot을 이용하는 user가 별도로 존재할 수
    있으며, 이 경우 특별한 권한이 추가적으로 필요하지는 않고, snapshot
    object에 대한 필요한 권한을 부여하면 된다.
    9. Database Link
    ================
    database link를 생성하기 전에 중요한 것은 replication 환경에 포함된 모든
    database는 고유한 global name을 가지고 있어야 한다. default global name은
    <db_name>과 동일하나 다음과 같이 문장을 통해 global name을 수정가능하다.
    그러므로 db_name이 같더라도 이렇게 global name을 수정하여 replication
    환경을 구성할 수 있다.
    SQL>ALTER DATABASE RENAME GLOBAL_NAME TO <new global name>;
    SQL>SELECT * FROM GLOBAL_NAME;
    updatable snapshot환경에서 database link가 제대로 구성되지 않으면 이후
    작업에 계속 문제가 생기므로 주의하여야 한다. 이 database link는 snapshot
    site에서 master site로만 구성하면 되며, 반대로 master site에서 snapshot
    site로 구성할 필요는 없다.
    (1) Public Database Links
    Net8 connection alias를 이용하여 다음과 같이 public database link를
    만든다. 이후 생성되는 private link는 using절을 포함하지 않게 되며,
    모두 public database link와 동일한 이름의 db link이름을 가져야 한다.
    (global_names=true이기 때문)
    SQL>CONNECT system/<password>
    SQL>CREATE PUBLIC DATABASE LINK <remote databases global name.world>
    USING 'Net8 alias';
    여기에서 표현한 Net8 alias는 snapshot site의 tnsnames.ora file에 정의
    되어 있어야만 한다.
    (2) Snapshot Administrator / Snapshot propagator / refresher
    snapshot administrator와 proxy snapshot administrator 다음과 같이 private
    database link가 필요하다.
    SQL>CONNECT snapadmin/<password>
    SQL>CREATE DATABASE LINK <remote databases global name.world>
    CONNECT TO snapproxy IDENTIFIED BY <password>;
    (3) Schema Owner (여기에서는 REPUSER로 명시한다)
    snapshot을 가지고 있는 모든 schema는 master site에 private database
    link를 생성해야 한다. 이때, "Schema to Schema" 와 "Schema to Proxy
    Refresher" 두가지를 고려할 수 있다.
    만약 link를 schema to schema방식으로 생성하게 되면, snapshot owner는
    쉽게 master site로 연결하여, master table에 DDL이나 DML을 수행가능하다.
    이것은 일반적으로 바람직하지 않으므로 master의 proxy refresher로
    private database link를 만들도록 권고된다. master에서 proxy refresher와
    proxy administrator가 동일한것이 일반적으로 결국 proxy administrtor에게
    연결하면 된다.
    이렇게 되면 snapshot의 schema owner는 proxy refresher user에 의해,
    master table에 대한 "select any table"권한은 가지게 되지만, DDL이나,
    DML은 허용되지 않으므로 더 안정적이다.
    SQL>CONNECT repuser/<password>
    SQL>CREATE DATABASE LINK <remote databases global name.world>
    CONNECT TO snapproxy IDENTIFIED BY <password>;
    (5) End User
    database link가 필요하지 않다.
    9.6 Testing Database Links
    database link생성 작업이 끝나면 다음과 같이 하여, 각 user별로 database
    link 생성이 올바로 되었는지 확인하도록 한다.
    SQL>CONNECT user/<password>
    SQL>SELECT * FROM DUAL@<database link name>
    10. schedule설정
    ================
    1 ~ 9번까지 성공적으로 수행되었다면 이제 replication manager를 이용하여,
    replication/snapshot group과 object를 추가할 수 있다.
    replication manager를 이용시 master site는 repadmin user로 접속하고,
    snapshot site는 snapadmin user로 접속하도록 한다.
    snapshot site의 변경 작업을 master site로 주기적으로 push시키고, 이렇게
    push된 data를 또 다른 주기로 purge시키는 scheduling이 필요하다.
    이것은 replication manager를 이용하려면, 아래 menu를 이용하면 된다.
    - Scheduling --> Scheduled Links
    - Database Information --> Purge Job Tab
    이 작업을 sql문으로 수행하려면 다음과 같은 문장을 snapshot site에서
    수행한다.
    SQL>CONNECT snapadmin/<password>
    SQL>BEGIN
    dbms_defer_sys.schedule_push(
    destination => '<destination databases global name>.WORLD',
    interval => '/*10:Mins*/ sysdate + 10/(60*24)',
    next_date => sysdate,
    stop_on_error => FALSE,
    delay_seconds => 0,
    parallelism => 1);
    SQL>END;
    SQL>/
    SQL>BEGIN
    dbms_defer_sys.schedule_purge(
    next_date => sysdate,
    interval => '/*1:Hr*/ sysdate + 1/24',
    delay_seconds => 0,
    rollback_segment => '');
    SQL>END;
    SQL>/

  • [Solved] Shutdown/Reboot takes a long time

    I do an upgrade every 5 days or so but it's been a while since I last rebooted--probably around 15-24 days. Since I haven't shutdown/rebooted for a while, I decided to do one today. I noticed that shutdown/reboot takes a long time, around 2-3 minutes whereas before, it would be instant and the behavior seems weird. Upon pressing shutdown or reboot:
    1. Monitors become completely black and searches for a signal (by switching HDMI, DVI, etc). PC still on
    2. After 1 minute, if reboot, I can hear the GPU fans spin like crazy. Shutdown doesn't do this, just quiet.
    3. After waiting another minute, some output shows up really fast and the PC is rebooted or shutdown
    This didn't happen before so I think it's probable that one of the updates did this. Unfortunately, I'm not sure how to tell which one.
    I followed the section "Diagnosing Shutdown Problems" here on how to debug shutdown problems. I've got the systemd shutdown log but I can't tell where the problem is:
    [ 0.000000] Initializing cgroup subsys cpuset
    [ 0.000000] Initializing cgroup subsys cpu
    [ 0.000000] Initializing cgroup subsys cpuacct
    [ 0.000000] Linux version 3.19.3-3-ARCH (builduser@tobias) (gcc version 4.9.2 20150304 (prerelease) (GCC) ) #1 SMP PREEMPT Wed Apr 8 14:10:00 CEST 2015
    [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=0a8d7720-6c75-4f1e-b2e4-04d8196aa0fb rw quiet
    [ 0.000000] e820: BIOS-provided physical RAM map:
    [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
    [ 0.000000] BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000bea34fff] usable
    [ 0.000000] BIOS-e820: [mem 0x00000000bea35000-0x00000000bea7dfff] ACPI NVS
    [ 0.000000] BIOS-e820: [mem 0x00000000bea7e000-0x00000000bea85fff] ACPI data
    [ 0.000000] BIOS-e820: [mem 0x00000000bea86000-0x00000000bf5f9fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000bf5fa000-0x00000000bf5fbfff] usable
    [ 0.000000] BIOS-e820: [mem 0x00000000bf5fc000-0x00000000bf60bfff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000bf60c000-0x00000000bf615fff] ACPI NVS
    [ 0.000000] BIOS-e820: [mem 0x00000000bf616000-0x00000000bf63afff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000bf63b000-0x00000000bf67dfff] ACPI NVS
    [ 0.000000] BIOS-e820: [mem 0x00000000bf67e000-0x00000000bf7fffff] usable
    [ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed3ffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000023f7fffff] usable
    [ 0.000000] NX (Execute Disable) protection: active
    [ 0.000000] SMBIOS 2.7 present.
    [ 0.000000] DMI: MSI MS-7673/P67A-G43 (MS-7673), BIOS V1.11 04/14/2011
    [ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
    [ 0.000000] AGP: No AGP bridge found
    [ 0.000000] e820: last_pfn = 0x23f800 max_arch_pfn = 0x400000000
    [ 0.000000] MTRR default type: uncachable
    [ 0.000000] MTRR fixed ranges enabled:
    [ 0.000000] 00000-9FFFF write-back
    [ 0.000000] A0000-BFFFF uncachable
    [ 0.000000] C0000-CFFFF write-protect
    [ 0.000000] D0000-E7FFF uncachable
    [ 0.000000] E8000-FFFFF write-protect
    [ 0.000000] MTRR variable ranges enabled:
    [ 0.000000] 0 base 000000000 mask E00000000 write-back
    [ 0.000000] 1 base 200000000 mask FC0000000 write-back
    [ 0.000000] 2 base 0C0000000 mask FC0000000 uncachable
    [ 0.000000] 3 base 23F800000 mask FFF800000 uncachable
    [ 0.000000] 4 disabled
    [ 0.000000] 5 disabled
    [ 0.000000] 6 disabled
    [ 0.000000] 7 disabled
    [ 0.000000] 8 disabled
    [ 0.000000] 9 disabled
    [ 0.000000] PAT configuration [0-7]: WB WC UC- UC WB WC UC- UC
    [ 0.000000] e820: update [mem 0xc0000000-0xffffffff] usable ==> reserved
    [ 0.000000] e820: last_pfn = 0xbf800 max_arch_pfn = 0x400000000
    [ 0.000000] found SMP MP-table at [mem 0x000fce60-0x000fce6f] mapped at [ffff8800000fce60]
    [ 0.000000] Scanning 1 areas for low memory corruption
    [ 0.000000] Base memory trampoline at [ffff880000097000] 97000 size 24576
    [ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
    [ 0.000000] [mem 0x00000000-0x000fffff] page 4k
    [ 0.000000] BRK [0x01b32000, 0x01b32fff] PGTABLE
    [ 0.000000] BRK [0x01b33000, 0x01b33fff] PGTABLE
    [ 0.000000] BRK [0x01b34000, 0x01b34fff] PGTABLE
    [ 0.000000] init_memory_mapping: [mem 0x23f600000-0x23f7fffff]
    [ 0.000000] [mem 0x23f600000-0x23f7fffff] page 2M
    [ 0.000000] BRK [0x01b35000, 0x01b35fff] PGTABLE
    [ 0.000000] init_memory_mapping: [mem 0x220000000-0x23f5fffff]
    [ 0.000000] [mem 0x220000000-0x23f5fffff] page 2M
    [ 0.000000] init_memory_mapping: [mem 0x200000000-0x21fffffff]
    [ 0.000000] [mem 0x200000000-0x21fffffff] page 2M
    [ 0.000000] init_memory_mapping: [mem 0x00100000-0xbea34fff]
    [ 0.000000] [mem 0x00100000-0x001fffff] page 4k
    [ 0.000000] [mem 0x00200000-0xbe9fffff] page 2M
    [ 0.000000] [mem 0xbea00000-0xbea34fff] page 4k
    [ 0.000000] init_memory_mapping: [mem 0xbf5fa000-0xbf5fbfff]
    [ 0.000000] [mem 0xbf5fa000-0xbf5fbfff] page 4k
    [ 0.000000] BRK [0x01b36000, 0x01b36fff] PGTABLE
    [ 0.000000] init_memory_mapping: [mem 0xbf67e000-0xbf7fffff]
    [ 0.000000] [mem 0xbf67e000-0xbf7fffff] page 4k
    [ 0.000000] BRK [0x01b37000, 0x01b37fff] PGTABLE
    [ 0.000000] init_memory_mapping: [mem 0x100000000-0x1ffffffff]
    [ 0.000000] [mem 0x100000000-0x1ffffffff] page 2M
    [ 0.000000] RAMDISK: [mem 0x3795c000-0x37ca5fff]
    [ 0.000000] ACPI: Early table checksum verification disabled
    [ 0.000000] ACPI: RSDP 0x00000000000F0450 000024 (v02 ALASKA)
    [ 0.000000] ACPI: XSDT 0x00000000BEA7E068 000054 (v01 ALASKA A M I 01072009 AMI 00010013)
    [ 0.000000] ACPI: FACP 0x00000000BEA85148 0000F4 (v04 ALASKA A M I 01072009 AMI 00010013)
    [ 0.000000] ACPI: DSDT 0x00000000BEA7E150 006FF4 (v02 ALASKA A M I 00000015 INTL 20051117)
    [ 0.000000] ACPI: FACS 0x00000000BF60DF80 000040
    [ 0.000000] ACPI: APIC 0x00000000BEA85240 000072 (v03 ALASKA A M I 01072009 AMI 00010013)
    [ 0.000000] ACPI: SSDT 0x00000000BEA852B8 000102 (v01 AMICPU PROC 00000001 MSFT 03000001)
    [ 0.000000] ACPI: MCFG 0x00000000BEA853C0 00003C (v01 ALASKA A M I 01072009 MSFT 00000097)
    [ 0.000000] ACPI: HPET 0x00000000BEA85400 000038 (v01 ALASKA A M I 01072009 AMI. 00000004)
    [ 0.000000] ACPI: ASF! 0x00000000BEA85438 0000A0 (v32 INTEL HCG 00000001 TFSM 000F4240)
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] No NUMA configuration found
    [ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000023f7fffff]
    [ 0.000000] NODE_DATA(0) allocated [mem 0x23f7f5000-0x23f7f8fff]
    [ 0.000000] [ffffea0000000000-ffffea0008ffffff] PMD -> [ffff880236e00000-ffff88023edfffff] on node 0
    [ 0.000000] Zone ranges:
    [ 0.000000] DMA [mem 0x00001000-0x00ffffff]
    [ 0.000000] DMA32 [mem 0x01000000-0xffffffff]
    [ 0.000000] Normal [mem 0x100000000-0x23f7fffff]
    [ 0.000000] Movable zone start for each node
    [ 0.000000] Early memory node ranges
    [ 0.000000] node 0: [mem 0x00001000-0x0009cfff]
    [ 0.000000] node 0: [mem 0x00100000-0xbea34fff]
    [ 0.000000] node 0: [mem 0xbf5fa000-0xbf5fbfff]
    [ 0.000000] node 0: [mem 0xbf67e000-0xbf7fffff]
    [ 0.000000] node 0: [mem 0x100000000-0x23f7fffff]
    [ 0.000000] Initmem setup node 0 [mem 0x00001000-0x23f7fffff]
    [ 0.000000] On node 0 totalpages: 2089813
    [ 0.000000] DMA zone: 64 pages used for memmap
    [ 0.000000] DMA zone: 21 pages reserved
    [ 0.000000] DMA zone: 3996 pages, LIFO batch:0
    [ 0.000000] DMA32 zone: 12143 pages used for memmap
    [ 0.000000] DMA32 zone: 777145 pages, LIFO batch:31
    [ 0.000000] Normal zone: 20448 pages used for memmap
    [ 0.000000] Normal zone: 1308672 pages, LIFO batch:31
    [ 0.000000] ACPI: PM-Timer IO Port: 0x408
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
    [ 0.000000] ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
    [ 0.000000] IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    [ 0.000000] ACPI: IRQ0 used by override.
    [ 0.000000] ACPI: IRQ9 used by override.
    [ 0.000000] Using ACPI (MADT) for SMP configuration information
    [ 0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
    [ 0.000000] smpboot: Allowing 4 CPUs, 0 hotplug CPUs
    [ 0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
    [ 0.000000] PM: Registered nosave memory: [mem 0x0009d000-0x0009dfff]
    [ 0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xbea35000-0xbea7dfff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xbea7e000-0xbea85fff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xbea86000-0xbf5f9fff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xbf5fc000-0xbf60bfff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xbf60c000-0xbf615fff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xbf616000-0xbf63afff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xbf63b000-0xbf67dfff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xbf800000-0xfed1bfff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed3ffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfed40000-0xfeffffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
    [ 0.000000] e820: [mem 0xbf800000-0xfed1bfff] available for PCI devices
    [ 0.000000] Booting paravirtualized kernel on bare hardware
    [ 0.000000] setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:4 nr_node_ids:1
    [ 0.000000] PERCPU: Embedded 31 pages/cpu @ffff88023f400000 s86336 r8192 d32448 u524288
    [ 0.000000] pcpu-alloc: s86336 r8192 d32448 u524288 alloc=1*2097152
    [ 0.000000] pcpu-alloc: [0] 0 1 2 3
    [ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 2057137
    [ 0.000000] Policy zone: Normal
    [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=0a8d7720-6c75-4f1e-b2e4-04d8196aa0fb rw quiet
    [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
    [ 0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340 using standard form
    [ 0.000000] AGP: Checking aperture...
    [ 0.000000] AGP: No AGP bridge found
    [ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
    [ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    [ 0.000000] Memory: 8146392K/8359252K available (5534K kernel code, 917K rwdata, 1744K rodata, 1164K init, 1156K bss, 212860K reserved, 0K cma-reserved)
    [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
    [ 0.000000] Preemptible hierarchical RCU implementation.
    [ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
    [ 0.000000] RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=4.
    [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
    [ 0.000000] NR_IRQS:8448 nr_irqs:456 16
    [ 0.000000] Console: colour dummy device 80x25
    [ 0.000000] console [tty0] enabled
    [ 0.000000] hpet clockevent registered
    [ 0.000000] tsc: Fast TSC calibration using PIT
    [ 0.000000] tsc: Detected 3299.649 MHz processor
    [ 0.000020] Calibrating delay loop (skipped), value calculated using timer frequency.. 6601.26 BogoMIPS (lpj=10998830)
    [ 0.000022] pid_max: default: 32768 minimum: 301
    [ 0.000025] ACPI: Core revision 20141107
    [ 0.002006] ACPI: All ACPI Tables successfully acquired
    [ 0.229873] Security Framework initialized
    [ 0.229877] Yama: becoming mindful.
    [ 0.230159] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
    [ 0.231159] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
    [ 0.231602] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
    [ 0.231607] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
    [ 0.231738] Initializing cgroup subsys memory
    [ 0.231741] Initializing cgroup subsys devices
    [ 0.231743] Initializing cgroup subsys freezer
    [ 0.231744] Initializing cgroup subsys net_cls
    [ 0.231745] Initializing cgroup subsys blkio
    [ 0.231759] CPU: Physical Processor ID: 0
    [ 0.231759] CPU: Processor Core ID: 0
    [ 0.231762] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
    ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
    [ 0.231764] mce: CPU supports 9 MCE banks
    [ 0.231772] CPU0: Thermal monitoring enabled (TM1)
    [ 0.231778] Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
    Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
    [ 0.231839] Freeing SMP alternatives memory: 20K (ffffffff81a0a000 - ffffffff81a0f000)
    [ 0.232422] ftrace: allocating 21171 entries in 83 pages
    [ 0.238717] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    [ 0.271684] smpboot: CPU0: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (fam: 06, model: 2a, stepping: 07)
    [ 0.271688] TSC deadline timer enabled
    [ 0.271700] Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, full-width counters, Intel PMU driver.
    [ 0.271711] perf_event_intel: PEBS disabled due to CPU errata, please upgrade microcode
    [ 0.271712] ... version: 3
    [ 0.271712] ... bit width: 48
    [ 0.271713] ... generic registers: 8
    [ 0.271714] ... value mask: 0000ffffffffffff
    [ 0.271714] ... max period: 0000ffffffffffff
    [ 0.271715] ... fixed-purpose events: 3
    [ 0.271715] ... event mask: 00000007000000ff
    [ 0.291699] x86: Booting SMP configuration:
    [ 0.291700] .... node #0, CPUs: #1
    [ 0.304842] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    [ 0.305029] #2 #3
    [ 0.334799] x86: Booted up 1 node, 4 CPUs
    [ 0.334802] smpboot: Total of 4 processors activated (26407.07 BogoMIPS)
    [ 0.336656] devtmpfs: initialized
    [ 0.338107] PM: Registering ACPI NVS region [mem 0xbea35000-0xbea7dfff] (299008 bytes)
    [ 0.338111] PM: Registering ACPI NVS region [mem 0xbf60c000-0xbf615fff] (40960 bytes)
    [ 0.338111] PM: Registering ACPI NVS region [mem 0xbf63b000-0xbf67dfff] (274432 bytes)
    [ 0.338196] pinctrl core: initialized pinctrl subsystem
    [ 0.338227] RTC time: 18:49:17, date: 04/22/15
    [ 0.338286] NET: Registered protocol family 16
    [ 0.349856] cpuidle: using governor ladder
    [ 0.363177] cpuidle: using governor menu
    [ 0.363192] ACPI: bus type PCI registered
    [ 0.363193] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
    [ 0.363233] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
    [ 0.363234] PCI: not using MMCONFIG
    [ 0.363235] PCI: Using configuration type 1 for base access
    [ 0.376685] ACPI: Added _OSI(Module Device)
    [ 0.376686] ACPI: Added _OSI(Processor Device)
    [ 0.376687] ACPI: Added _OSI(3.0 _SCP Extensions)
    [ 0.376688] ACPI: Added _OSI(Processor Aggregator Device)
    [ 0.377668] ACPI: Executed 1 blocks of module-level executable AML code
    [ 0.378832] ACPI: Dynamic OEM Table Load:
    [ 0.378835] ACPI: SSDT 0xFFFF880235BFDE40 000084 (v01 AMI CST 00000001 MSFT 03000001)
    [ 0.379146] ACPI: Interpreter enabled
    [ 0.379150] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20141107/hwxface-580)
    [ 0.379156] ACPI: (supports S0 S1 S3 S4 S5)
    [ 0.379157] ACPI: Using IOAPIC for interrupt routing
    [ 0.379168] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
    [ 0.379198] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
    [ 0.379380] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    [ 0.379496] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    [ 0.381659] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    [ 0.381662] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
    [ 0.381725] acpi PNP0A08:00: _OSC: platform does not support [PCIeCapability]
    [ 0.381755] acpi PNP0A08:00: _OSC: not requesting control; platform does not support [PCIeCapability]
    [ 0.381757] acpi PNP0A08:00: _OSC: OS requested [PCIeHotplug PME AER PCIeCapability]
    [ 0.381758] acpi PNP0A08:00: _OSC: platform willing to grant [PCIeHotplug PME AER]
    [ 0.381759] acpi PNP0A08:00: _OSC failed (AE_SUPPORT); disabling ASPM
    [ 0.381932] PCI host bridge to bus 0000:00
    [ 0.381934] pci_bus 0000:00: root bus resource [bus 00-ff]
    [ 0.381935] pci_bus 0000:00: root bus resource [io 0x0000-0x03af]
    [ 0.381936] pci_bus 0000:00: root bus resource [io 0x03e0-0x0cf7]
    [ 0.381936] pci_bus 0000:00: root bus resource [io 0x03b0-0x03df]
    [ 0.381937] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    [ 0.381938] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    [ 0.381939] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff]
    [ 0.381940] pci_bus 0000:00: root bus resource [mem 0xc0000000-0xffffffff]
    [ 0.381945] pci 0000:00:00.0: [8086:0100] type 00 class 0x060000
    [ 0.381993] pci 0000:00:01.0: [8086:0101] type 01 class 0x060400
    [ 0.382014] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
    [ 0.382032] pci 0000:00:01.0: System wakeup disabled by ACPI
    [ 0.382079] pci 0000:00:16.0: [8086:1c3a] type 00 class 0x078000
    [ 0.382098] pci 0000:00:16.0: reg 0x10: [mem 0xfe708000-0xfe70800f 64bit]
    [ 0.382164] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
    [ 0.382218] pci 0000:00:1a.0: [8086:1c2d] type 00 class 0x0c0320
    [ 0.382235] pci 0000:00:1a.0: reg 0x10: [mem 0xfe707000-0xfe7073ff]
    [ 0.382315] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
    [ 0.382339] pci 0000:00:1a.0: System wakeup disabled by ACPI
    [ 0.382365] pci 0000:00:1b.0: [8086:1c20] type 00 class 0x040300
    [ 0.382378] pci 0000:00:1b.0: reg 0x10: [mem 0xfe700000-0xfe703fff 64bit]
    [ 0.382443] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    [ 0.382493] pci 0000:00:1c.0: [8086:1c10] type 01 class 0x060400
    [ 0.382628] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    [ 0.382664] pci 0000:00:1c.0: System wakeup disabled by ACPI
    [ 0.382689] pci 0000:00:1c.4: [8086:244e] type 01 class 0x060401
    [ 0.382761] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
    [ 0.382787] pci 0000:00:1c.4: System wakeup disabled by ACPI
    [ 0.382810] pci 0000:00:1c.5: [8086:1c1a] type 01 class 0x060400
    [ 0.382882] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
    [ 0.382908] pci 0000:00:1c.5: System wakeup disabled by ACPI
    [ 0.382932] pci 0000:00:1c.6: [8086:1c1c] type 01 class 0x060400
    [ 0.383004] pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold
    [ 0.383029] pci 0000:00:1c.6: System wakeup disabled by ACPI
    [ 0.383056] pci 0000:00:1d.0: [8086:1c26] type 00 class 0x0c0320
    [ 0.383074] pci 0000:00:1d.0: reg 0x10: [mem 0xfe706000-0xfe7063ff]
    [ 0.383154] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
    [ 0.383181] pci 0000:00:1d.0: System wakeup disabled by ACPI
    [ 0.383206] pci 0000:00:1f.0: [8086:1c46] type 00 class 0x060100
    [ 0.383340] pci 0000:00:1f.2: [8086:1c02] type 00 class 0x010601
    [ 0.383355] pci 0000:00:1f.2: reg 0x10: [io 0xf070-0xf077]
    [ 0.383361] pci 0000:00:1f.2: reg 0x14: [io 0xf060-0xf063]
    [ 0.383366] pci 0000:00:1f.2: reg 0x18: [io 0xf050-0xf057]
    [ 0.383372] pci 0000:00:1f.2: reg 0x1c: [io 0xf040-0xf043]
    [ 0.383378] pci 0000:00:1f.2: reg 0x20: [io 0xf020-0xf03f]
    [ 0.383384] pci 0000:00:1f.2: reg 0x24: [mem 0xfe705000-0xfe7057ff]
    [ 0.383422] pci 0000:00:1f.2: PME# supported from D3hot
    [ 0.383461] pci 0000:00:1f.3: [8086:1c22] type 00 class 0x0c0500
    [ 0.383473] pci 0000:00:1f.3: reg 0x10: [mem 0xfe704000-0xfe7040ff 64bit]
    [ 0.383490] pci 0000:00:1f.3: reg 0x20: [io 0xf000-0xf01f]
    [ 0.383561] pci 0000:01:00.0: [1002:6719] type 00 class 0x030000
    [ 0.383571] pci 0000:01:00.0: reg 0x10: [mem 0xc0000000-0xcfffffff 64bit pref]
    [ 0.383579] pci 0000:01:00.0: reg 0x18: [mem 0xfe620000-0xfe63ffff 64bit]
    [ 0.383584] pci 0000:01:00.0: reg 0x20: [io 0xe000-0xe0ff]
    [ 0.383593] pci 0000:01:00.0: reg 0x30: [mem 0xfe600000-0xfe61ffff pref]
    [ 0.383621] pci 0000:01:00.0: supports D1 D2
    [ 0.383650] pci 0000:01:00.1: [1002:aa80] type 00 class 0x040300
    [ 0.383660] pci 0000:01:00.1: reg 0x10: [mem 0xfe640000-0xfe643fff 64bit]
    [ 0.383708] pci 0000:01:00.1: supports D1 D2
    [ 0.389829] pci 0000:00:01.0: PCI bridge to [bus 01]
    [ 0.389830] pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
    [ 0.389832] pci 0000:00:01.0: bridge window [mem 0xfe600000-0xfe6fffff]
    [ 0.389833] pci 0000:00:01.0: bridge window [mem 0xc0000000-0xcfffffff 64bit pref]
    [ 0.389906] pci 0000:00:1c.0: PCI bridge to [bus 02]
    [ 0.389985] pci 0000:03:00.0: [1b21:1080] type 01 class 0x060400
    [ 0.390139] pci 0000:03:00.0: supports D1 D2
    [ 0.390140] pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.396493] pci 0000:00:1c.4: PCI bridge to [bus 03-04] (subtractive decode)
    [ 0.396501] pci 0000:00:1c.4: bridge window [io 0x0000-0x03af] (subtractive decode)
    [ 0.396502] pci 0000:00:1c.4: bridge window [io 0x03e0-0x0cf7] (subtractive decode)
    [ 0.396503] pci 0000:00:1c.4: bridge window [io 0x03b0-0x03df] (subtractive decode)
    [ 0.396504] pci 0000:00:1c.4: bridge window [io 0x0d00-0xffff] (subtractive decode)
    [ 0.396505] pci 0000:00:1c.4: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    [ 0.396506] pci 0000:00:1c.4: bridge window [mem 0x000c0000-0x000dffff] (subtractive decode)
    [ 0.396507] pci 0000:00:1c.4: bridge window [mem 0xc0000000-0xffffffff] (subtractive decode)
    [ 0.396651] pci 0000:03:00.0: PCI bridge to [bus 04]
    [ 0.396745] pci 0000:05:00.0: [1033:0194] type 00 class 0x0c0330
    [ 0.396772] pci 0000:05:00.0: reg 0x10: [mem 0xfe500000-0xfe501fff 64bit]
    [ 0.396910] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
    [ 0.403155] pci 0000:00:1c.5: PCI bridge to [bus 05]
    [ 0.403160] pci 0000:00:1c.5: bridge window [mem 0xfe500000-0xfe5fffff]
    [ 0.403227] pci 0000:06:00.0: [10ec:8168] type 00 class 0x020000
    [ 0.403248] pci 0000:06:00.0: reg 0x10: [io 0xd000-0xd0ff]
    [ 0.403279] pci 0000:06:00.0: reg 0x18: [mem 0xd0004000-0xd0004fff 64bit pref]
    [ 0.403298] pci 0000:06:00.0: reg 0x20: [mem 0xd0000000-0xd0003fff 64bit pref]
    [ 0.403403] pci 0000:06:00.0: supports D1 D2
    [ 0.403404] pci 0000:06:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.409816] pci 0000:00:1c.6: PCI bridge to [bus 06]
    [ 0.409819] pci 0000:00:1c.6: bridge window [io 0xd000-0xdfff]
    [ 0.409826] pci 0000:00:1c.6: bridge window [mem 0xd0000000-0xd00fffff 64bit pref]
    [ 0.410049] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
    [ 0.410074] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
    [ 0.410098] ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 6 10 11 12 14 15)
    [ 0.410122] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
    [ 0.410146] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
    [ 0.410170] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
    [ 0.410194] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *5 6 7 10 11 12 14 15)
    [ 0.410218] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *7 10 11 12 14 15)
    [ 0.410250] ACPI: Enabled 3 GPEs in block 00 to 3F
    [ 0.410300] vgaarb: setting as boot device: PCI:0000:01:00.0
    [ 0.410301] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
    [ 0.410302] vgaarb: loaded
    [ 0.410303] vgaarb: bridge control possible 0000:01:00.0
    [ 0.410339] PCI: Using ACPI for IRQ routing
    [ 0.415815] PCI: pci_cache_line_size set to 64 bytes
    [ 0.415855] e820: reserve RAM buffer [mem 0x0009d800-0x0009ffff]
    [ 0.415856] e820: reserve RAM buffer [mem 0xbea35000-0xbfffffff]
    [ 0.415857] e820: reserve RAM buffer [mem 0xbf5fc000-0xbfffffff]
    [ 0.415857] e820: reserve RAM buffer [mem 0xbf800000-0xbfffffff]
    [ 0.415858] e820: reserve RAM buffer [mem 0x23f800000-0x23fffffff]
    [ 0.415918] NetLabel: Initializing
    [ 0.415919] NetLabel: domain hash size = 128
    [ 0.415919] NetLabel: protocols = UNLABELED CIPSOv4
    [ 0.415927] NetLabel: unlabeled traffic allowed by default
    [ 0.415940] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
    [ 0.415942] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
    [ 0.417956] Switched to clocksource hpet
    [ 0.420722] pnp: PnP ACPI init
    [ 0.420798] system 00:00: [mem 0xfed10000-0xfed19fff] has been reserved
    [ 0.420799] system 00:00: [mem 0xe0000000-0xefffffff] has been reserved
    [ 0.420800] system 00:00: [mem 0xfed90000-0xfed93fff] has been reserved
    [ 0.420801] system 00:00: [mem 0xfed20000-0xfed3ffff] has been reserved
    [ 0.420802] system 00:00: [mem 0xfee00000-0xfee0ffff] has been reserved
    [ 0.420804] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
    [ 0.420902] system 00:01: [io 0x0a00-0x0a0f] has been reserved
    [ 0.420903] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.420993] pnp 00:02: [dma 0 disabled]
    [ 0.421016] pnp 00:02: Plug and Play ACPI device, IDs PNP0501 (active)
    [ 0.421032] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
    [ 0.421058] system 00:04: [io 0x04d0-0x04d1] has been reserved
    [ 0.421059] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.421149] system 00:05: [io 0x0400-0x0453] could not be reserved
    [ 0.421150] system 00:05: [io 0x0458-0x047f] has been reserved
    [ 0.421151] system 00:05: [io 0x1180-0x119f] has been reserved
    [ 0.421152] system 00:05: [io 0x0500-0x057f] has been reserved
    [ 0.421153] system 00:05: [mem 0xfed1c000-0xfed1ffff] has been reserved
    [ 0.421154] system 00:05: [mem 0xfec00000-0xfecfffff] could not be reserved
    [ 0.421155] system 00:05: [mem 0xfed08000-0xfed08fff] has been reserved
    [ 0.421157] system 00:05: [mem 0xff000000-0xffffffff] has been reserved
    [ 0.421158] system 00:05: Plug and Play ACPI device, IDs PNP0c01 (active)
    [ 0.421187] system 00:06: [io 0x0454-0x0457] has been reserved
    [ 0.421188] system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
    [ 0.421295] pnp: PnP ACPI: found 7 devices
    [ 0.427004] pci 0000:00:01.0: PCI bridge to [bus 01]
    [ 0.427006] pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
    [ 0.427007] pci 0000:00:01.0: bridge window [mem 0xfe600000-0xfe6fffff]
    [ 0.427009] pci 0000:00:01.0: bridge window [mem 0xc0000000-0xcfffffff 64bit pref]
    [ 0.427011] pci 0000:00:1c.0: PCI bridge to [bus 02]
    [ 0.427026] pci 0000:03:00.0: PCI bridge to [bus 04]
    [ 0.427044] pci 0000:00:1c.4: PCI bridge to [bus 03-04]
    [ 0.427053] pci 0000:00:1c.5: PCI bridge to [bus 05]
    [ 0.427056] pci 0000:00:1c.5: bridge window [mem 0xfe500000-0xfe5fffff]
    [ 0.427063] pci 0000:00:1c.6: PCI bridge to [bus 06]
    [ 0.427064] pci 0000:00:1c.6: bridge window [io 0xd000-0xdfff]
    [ 0.427070] pci 0000:00:1c.6: bridge window [mem 0xd0000000-0xd00fffff 64bit pref]
    [ 0.427075] pci_bus 0000:00: resource 4 [io 0x0000-0x03af]
    [ 0.427076] pci_bus 0000:00: resource 5 [io 0x03e0-0x0cf7]
    [ 0.427077] pci_bus 0000:00: resource 6 [io 0x03b0-0x03df]
    [ 0.427077] pci_bus 0000:00: resource 7 [io 0x0d00-0xffff]
    [ 0.427078] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
    [ 0.427079] pci_bus 0000:00: resource 9 [mem 0x000c0000-0x000dffff]
    [ 0.427080] pci_bus 0000:00: resource 10 [mem 0xc0000000-0xffffffff]
    [ 0.427081] pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
    [ 0.427082] pci_bus 0000:01: resource 1 [mem 0xfe600000-0xfe6fffff]
    [ 0.427083] pci_bus 0000:01: resource 2 [mem 0xc0000000-0xcfffffff 64bit pref]
    [ 0.427084] pci_bus 0000:03: resource 4 [io 0x0000-0x03af]
    [ 0.427085] pci_bus 0000:03: resource 5 [io 0x03e0-0x0cf7]
    [ 0.427086] pci_bus 0000:03: resource 6 [io 0x03b0-0x03df]
    [ 0.427087] pci_bus 0000:03: resource 7 [io 0x0d00-0xffff]
    [ 0.427087] pci_bus 0000:03: resource 8 [mem 0x000a0000-0x000bffff]
    [ 0.427088] pci_bus 0000:03: resource 9 [mem 0x000c0000-0x000dffff]
    [ 0.427089] pci_bus 0000:03: resource 10 [mem 0xc0000000-0xffffffff]
    [ 0.427090] pci_bus 0000:05: resource 1 [mem 0xfe500000-0xfe5fffff]
    [ 0.427091] pci_bus 0000:06: resource 0 [io 0xd000-0xdfff]
    [ 0.427092] pci_bus 0000:06: resource 2 [mem 0xd0000000-0xd00fffff 64bit pref]
    [ 0.427107] NET: Registered protocol family 2
    [ 0.427218] TCP established hash table entries: 65536 (order: 7, 524288 bytes)
    [ 0.427305] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    [ 0.427411] TCP: Hash tables configured (established 65536 bind 65536)
    [ 0.427422] TCP: reno registered
    [ 0.427428] UDP hash table entries: 4096 (order: 5, 131072 bytes)
    [ 0.427446] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
    [ 0.427479] NET: Registered protocol family 1
    [ 0.427627] pci 0000:01:00.0: Video device with shadowed ROM
    [ 0.427703] PCI: CLS 64 bytes, default 64
    [ 0.427731] Unpacking initramfs...
    [ 0.458276] Freeing initrd memory: 3368K (ffff88003795c000 - ffff880037ca6000)
    [ 0.458282] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
    [ 0.458284] software IO TLB [mem 0xbaa35000-0xbea35000] (64MB) mapped at [ffff8800baa35000-ffff8800bea34fff]
    [ 0.458388] RAPL PMU detected, hw unit 2^-16 Joules, API unit is 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer
    [ 0.458447] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x12
    [ 0.458451] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x12
    [ 0.458455] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x12
    [ 0.458459] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x12
    [ 0.458489] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
    [ 0.458503] Scanning for low memory corruption every 60 seconds
    [ 0.458643] futex hash table entries: 1024 (order: 4, 65536 bytes)
    [ 0.458653] Initialise system trusted keyring
    [ 0.458879] HugeTLB registered 2 MB page size, pre-allocated 0 pages
    [ 0.459596] zpool: loaded
    [ 0.459598] zbud: loaded
    [ 0.459684] VFS: Disk quotas dquot_6.5.2
    [ 0.459702] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    [ 0.459788] Key type big_key registered
    [ 0.459886] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    [ 0.459910] io scheduler noop registered
    [ 0.459911] io scheduler deadline registered
    [ 0.459926] io scheduler cfq registered (default)
    [ 0.460230] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    [ 0.460238] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
    [ 0.460245] vesafb: mode is 1400x1050x32, linelength=5632, pages=0
    [ 0.460245] vesafb: scrolling: redraw
    [ 0.460246] vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0
    [ 0.460257] vesafb: framebuffer at 0xc0000000, mapped to 0xffffc90010e80000, using 5824k, total 5824k
    [ 0.507010] Console: switching to colour frame buffer device 175x65
    [ 0.553487] fb0: VESA VGA frame buffer device
    [ 0.553501] intel_idle: MWAIT substates: 0x1120
    [ 0.553502] intel_idle: v0.4 model 0x2A
    [ 0.553502] intel_idle: lapic_timer_reliable_states 0xffffffff
    [ 0.553594] GHES: HEST is not enabled!
    [ 0.553630] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    [ 0.574150] 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
    [ 0.574369] Linux agpgart interface v0.103
    [ 0.574402] rtc_cmos 00:03: RTC can wake from S4
    [ 0.574506] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
    [ 0.574530] rtc_cmos 00:03: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
    [ 0.574537] Intel P-state driver initializing.
    [ 0.574635] ledtrig-cpu: registered to indicate activity on CPUs
    [ 0.575069] TCP: cubic registered
    [ 0.575206] NET: Registered protocol family 10
    [ 0.575527] NET: Registered protocol family 17
    [ 0.576245] Loading compiled-in X.509 certificates
    [ 0.576267] registered taskstats version 1
    [ 0.577040] Magic number: 11:338:848
    [ 0.577156] rtc_cmos 00:03: setting system clock to 2015-04-22 18:49:17 UTC (1429728557)
    [ 0.577255] PM: Hibernation image not present or could not be loaded.
    [ 0.577672] Freeing unused kernel memory: 1164K (ffffffff818e7000 - ffffffff81a0a000)
    [ 0.577674] Write protecting the kernel read-only data: 8192k
    [ 0.578177] Freeing unused kernel memory: 600K (ffff88000156a000 - ffff880001600000)
    [ 0.578369] Freeing unused kernel memory: 304K (ffff8800017b4000 - ffff880001800000)
    [ 0.586926] random: systemd-tmpfile urandom read with 1 bits of entropy available
    [ 0.594161] i8042: PNP: No PS/2 controller found. Probing ports directly.
    [ 0.594538] serio: i8042 KBD port at 0x60,0x64 irq 1
    [ 0.594602] serio: i8042 AUX port at 0x60,0x64 irq 12
    [ 0.596674] ACPI: bus type USB registered
    [ 0.596690] usbcore: registered new interface driver usbfs
    [ 0.596697] usbcore: registered new interface driver hub
    [ 0.596714] usbcore: registered new device driver usb
    [ 0.596929] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    [ 0.597010] ehci-pci: EHCI PCI platform driver
    [ 0.597090] ehci-pci 0000:00:1a.0: EHCI Host Controller
    [ 0.597095] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
    [ 0.597107] ehci-pci 0000:00:1a.0: debug port 2
    [ 0.598329] SCSI subsystem initialized
    [ 0.600997] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
    [ 0.601009] ehci-pci 0000:00:1a.0: irq 16, io mem 0xfe707000
    [ 0.601141] libata version 3.00 loaded.
    [ 0.607823] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
    [ 0.607929] hub 1-0:1.0: USB hub found
    [ 0.607934] hub 1-0:1.0: 2 ports detected
    [ 0.608004] xhci_hcd 0000:05:00.0: xHCI Host Controller
    [ 0.608009] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 2
    [ 0.608319] hub 2-0:1.0: USB hub found
    [ 0.608327] hub 2-0:1.0: 2 ports detected
    [ 0.608382] xhci_hcd 0000:05:00.0: xHCI Host Controller
    [ 0.608384] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 3
    [ 0.608386] ehci-pci 0000:00:1d.0: EHCI Host Controller
    [ 0.608389] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 4
    [ 0.608405] ehci-pci 0000:00:1d.0: debug port 2
    [ 0.611688] hub 3-0:1.0: USB hub found
    [ 0.611696] hub 3-0:1.0: 2 ports detected
    [ 0.612303] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
    [ 0.612313] ehci-pci 0000:00:1d.0: irq 23, io mem 0xfe706000
    [ 0.621118] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
    [ 0.621236] hub 4-0:1.0: USB hub found
    [ 0.621248] hub 4-0:1.0: 2 ports detected
    [ 0.621321] ahci 0000:00:1f.2: version 3.0
    [ 0.634481] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x3f impl SATA mode
    [ 0.634487] ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pio slum part ems apst
    [ 0.668448] scsi host0: ahci
    [ 0.668750] scsi host1: ahci
    [ 0.669100] scsi host2: ahci
    [ 0.669412] scsi host3: ahci
    [ 0.669697] scsi host4: ahci
    [ 0.669967] scsi host5: ahci
    [ 0.670051] ata1: SATA max UDMA/133 abar m2048@0xfe705000 port 0xfe705100 irq 30
    [ 0.670054] ata2: SATA max UDMA/133 abar m2048@0xfe705000 port 0xfe705180 irq 30
    [ 0.670057] ata3: SATA max UDMA/133 abar m2048@0xfe705000 port 0xfe705200 irq 30
    [ 0.670059] ata4: SATA max UDMA/133 abar m2048@0xfe705000 port 0xfe705280 irq 30
    [ 0.670061] ata5: SATA max UDMA/133 abar m2048@0xfe705000 port 0xfe705300 irq 30
    [ 0.670064] ata6: SATA max UDMA/133 abar m2048@0xfe705000 port 0xfe705380 irq 30
    [ 0.914200] usb 1-1: new high-speed USB device number 2 using ehci-pci
    [ 0.927545] usb 4-1: new high-speed USB device number 2 using ehci-pci
    [ 0.987472] ata5: SATA link down (SStatus 0 SControl 300)
    [ 0.987497] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [ 0.987521] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [ 0.987543] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [ 0.987563] ata6: SATA link down (SStatus 0 SControl 300)
    [ 0.987584] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    [ 0.987877] ata2.00: supports DRM functions and may not be fully accessible
    [ 0.988115] ata3.00: ATAPI: TSSTcorp CDDVDW SH-S243D, SB00, max UDMA/100
    [ 0.988210] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
    [ 0.988214] ata1.00: ATA-9: Samsung SSD 840 Series, DXT07B0Q, max UDMA/133
    [ 0.988217] ata1.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
    [ 0.988682] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
    [ 0.988746] ata1.00: configured for UDMA/133
    [ 0.988881] ata3.00: configured for UDMA/100
    [ 0.989027] scsi 0:0:0:0: Direct-Access ATA Samsung SSD 840 7B0Q PQ: 0 ANSI: 5
    [ 0.989649] ata4.00: ATA-8: WDC WD1002FAEX-00Z3A0, 05.01D05, max UDMA/133
    [ 0.989653] ata4.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
    [ 0.990752] ata2.00: disabling queued TRIM support
    [ 0.990755] ata2.00: ATA-9: Crucial_CT240M500SSD1, MU05, max UDMA/133
    [ 0.990757] ata2.00: 468862128 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
    [ 0.992466] ata4.00: configured for UDMA/133
    [ 0.994299] ata2.00: supports DRM functions and may not be fully accessible
    [ 0.997177] ata2.00: disabling queued TRIM support
    [ 1.000401] ata2.00: configured for UDMA/133
    [ 1.000669] scsi 1:0:0:0: Direct-Access ATA Crucial_CT240M50 MU05 PQ: 0 ANSI: 5
    [ 1.001813] scsi 2:0:0:0: CD-ROM TSSTcorp CDDVDW SH-S243D SB00 PQ: 0 ANSI: 5
    [ 1.011521] scsi 3:0:0:0: Direct-Access ATA WDC WD1002FAEX-0 1D05 PQ: 0 ANSI: 5
    [ 1.015296] ata1.00: Enabling discard_zeroes_data
    [ 1.015310] sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/111 GiB)
    [ 1.015364] sd 0:0:0:0: [sda] Write Protect is off
    [ 1.015367] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    [ 1.015385] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 1.015513] sd 1:0:0:0: [sdb] 468862128 512-byte logical blocks: (240 GB/223 GiB)
    [ 1.015517] sd 1:0:0:0: [sdb] 4096-byte physical blocks
    [ 1.015524] ata1.00: Enabling discard_zeroes_data
    [ 1.015532] sd 3:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
    [ 1.015618] sd 3:0:0:0: [sdc] Write Protect is off
    [ 1.015621] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
    [ 1.015636] sd 1:0:0:0: [sdb] Write Protect is off
    [ 1.015641] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
    [ 1.015657] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 1.015717] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 1.015779] sda: sda1 sda2
    [ 1.016099] ata1.00: Enabling discard_zeroes_data
    [ 1.016176] sd 0:0:0:0: [sda] Attached SCSI disk
    [ 1.016225] sdb: sdb1
    [ 1.016696] sd 1:0:0:0: [sdb] Attached SCSI disk
    [ 1.022237] sdc: sdc1 sdc2
    [ 1.022726] sd 3:0:0:0: [sdc] Attached SCSI disk
    [ 1.025940] sr 2:0:0:0: [sr0] scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
    [ 1.025945] cdrom: Uniform CD-ROM driver Revision: 3.20
    [ 1.026137] sr 2:0:0:0: Attached scsi CD-ROM sr0
    [ 1.038098] hub 1-1:1.0: USB hub found
    [ 1.038285] hub 1-1:1.0: 6 ports detected
    [ 1.051455] hub 4-1:1.0: USB hub found
    [ 1.051648] hub 4-1:1.0: 8 ports detected
    [ 1.298000] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
    [ 1.303924] usb 1-1.4: new high-speed USB device number 3 using ehci-pci
    [ 1.317239] usb 4-1.2: new full-speed USB device number 3 using ehci-pci
    [ 1.443336] systemd[1]: systemd 219 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD +IDN)
    [ 1.443537] systemd[1]: Detected architecture 'x86-64'.
    [ 1.443740] systemd[1]: Set hostname to <arch>.
    [ 1.460317] tsc: Refined TSC clocksource calibration: 3300.020 MHz
    [ 1.473794] usb 1-1.5: new high-speed USB device number 4 using ehci-pci
    [ 1.497743] systemd[1]: Unit type .busname is not supported on this system.
    [ 1.537625] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
    [ 1.537643] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
    [ 1.537662] systemd[1]: Reached target Remote File Systems.
    [ 1.537672] systemd[1]: Starting Remote File Systems.
    [ 1.537692] systemd[1]: Reached target Encrypted Volumes.
    [ 1.537701] systemd[1]: Starting Encrypted Volumes.
    [ 1.537748] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
    [ 1.537759] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
    [ 1.537800] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    [ 1.537810] systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
    [ 1.538002] systemd[1]: Created slice Root Slice.
    [ 1.538014] systemd[1]: Starting Root Slice.
    [ 1.538060] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
    [ 1.538070] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
    [ 1.538120] systemd[1]: Listening on Journal Socket.
    [ 1.538134] systemd[1]: Starting Journal Socket.
    [ 1.538265] systemd[1]: Created slice User and Session Slice.
    [ 1.538276] systemd[1]: Starting User and Session Slice.
    [ 1.545589] systemd[1]: Listening on Journal Audit Socket.
    [ 1.545747] systemd[1]: Created slice System Slice.
    [ 1.545765] systemd[1]: Starting System Slice.
    [ 1.546248] systemd[1]: Mounting Huge Pages File System...
    [ 1.546789] systemd[1]: Mounting Debug File System...
    [ 1.546970] systemd[1]: Created slice system-dhcpcd.slice.
    [ 1.546987] systemd[1]: Starting system-dhcpcd.slice.
    [ 1.547561] systemd[1]: Starting Create list of required static device nodes for the current kernel...
    [ 1.548678] systemd[1]: Starting Setup Virtual Console...
    [ 1.549285] systemd[1]: Started Set Up Additional Binary Formats.
    [ 1.550613] systemd[1]: Starting Load Kernel Modules...
    [ 1.550645] systemd[1]: Started File System Check on Root Device.
    [ 1.551159] systemd[1]: Starting Remount Root and Kernel File Systems...
    [ 1.551679] systemd[1]: Mounting POSIX Message Queue File System...
    [ 1.551836] systemd[1]: Created slice system-getty.slice.
    [ 1.551850] systemd[1]: Starting system-getty.slice.
    [ 1.551870] systemd[1]: Reached target Slices.
    [ 1.551883] systemd[1]: Starting Slices.
    [ 1.551931] systemd[1]: Listening on udev Kernel Socket.
    [ 1.551941] systemd[1]: Starting udev Kernel Socket.
    [ 1.551986] systemd[1]: Listening on Journal Socket (/dev/log).
    [ 1.551997] systemd[1]: Starting Journal Socket (/dev/log).
    [ 1.552492] systemd[1]: Starting Journal Service...
    [ 1.552545] systemd[1]: Listening on Device-mapper event daemon FIFOs.
    [ 1.552561] systemd[1]: Starting Device-mapper event daemon FIFOs.
    [ 1.552600] systemd[1]: Listening on udev Control Socket.
    [ 1.552611] systemd[1]: Starting udev Control Socket.
    [ 1.552659] systemd[1]: Listening on LVM2 metadata daemon socket.
    [ 1.552669] systemd[1]: Starting LVM2 metadata daemon socket.
    [ 1.552689] systemd[1]: Reached target Login Prompts.
    [ 1.552701] systemd[1]: Starting Login Prompts.
    [ 1.553185] systemd[1]: Starting udev Coldplug all Devices...
    [ 1.553231] systemd[1]: Listening on Delayed Shutdown Socket.
    [ 1.553249] systemd[1]: Starting Delayed Shutdown Socket.
    [ 1.554439] EXT4-fs (sdb1): re-mounted. Opts: data=ordered
    [ 1.555736] systemd[1]: Mounting Temporary Directory...
    [ 1.556329] systemd[1]: Mounted POSIX Message Queue File System.
    [ 1.556363] systemd[1]: Mounted Huge Pages File System.
    [ 1.556388] systemd[1]: Mounted Debug File System.
    [ 1.556779] systemd[1]: Started Create list of required static device nodes for the current kernel.
    [ 1.557030] systemd[1]: Started Setup Virtual Console.
    [ 1.557256] systemd[1]: Started Remount Root and Kernel File Systems.
    [ 1.557431] systemd[1]: Mounted Temporary Directory.
    [ 1.558591] hub 1-1.5:1.0: USB hub found
    [ 1.558901] hub 1-1.5:1.0: 4 ports detected
    [ 1.560366] vboxdrv: Found 4 processor cores.
    [ 1.561065] vboxdrv: fAsync=0 offMin=0x2ca offMax=0x6c0c
    [ 1.561137] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
    [ 1.561139] vboxdrv: Successfully loaded version 4.3.26_OSE (interface 0x001a000a).
    [ 1.561712] systemd[1]: Started Load Kernel Modules.
    [ 1.568012] systemd-journald[149]: Failed to set file attributes: Inappropriate ioctl for device
    [ 1.569830] systemd[1]: Started udev Coldplug all Devices.
    [ 1.575918] systemd[1]: Mounted FUSE Control File System.
    [ 1.576374] systemd[1]: Mounting Configuration File System...
    [ 1.576805] systemd[1]: Starting Apply Kernel Variables...
    [ 1.576856] systemd[1]: Started Rebuild Dynamic Linker Cache.
    [ 1.582712] systemd[1]: Started Rebuild Hardware Database.
    [ 1.582739] systemd[1]: Started First Boot Wizard.
    [ 1.582757] systemd[1]: Started Create System Users.
    [ 1.583212] systemd[1]: Starting Load/Save Random Seed...
    [ 1.583784] systemd[1]: Starting Create Static Device Nodes in /dev...
    [ 1.584599] systemd[1]: Mounted Configuration File System.
    [ 1.587256] systemd[1]: Started Load/Save Random Seed.
    [ 1.589801] systemd[1]: Started Apply Kernel Variables.
    [ 1.607967] systemd[1]: Started Create Static Device Nodes in /dev.
    [ 1.608452] systemd[1]: Starting udev Kernel Device Manager...
    [ 1.608476] systemd[1]: Reached target Local File Systems (Pre).
    [ 1.608492] systemd[1]: Starting Local File Systems (Pre).
    [ 1.626961] usb 1-1.6: new low-speed USB device number 5 using ehci-pci
    [ 1.637443] systemd[1]: Started udev Kernel Device Manager.
    [ 1.649393] systemd[1]: Started Journal Service.
    [ 1.653641] systemd-journald[149]: Received request to flush runtime journal from PID 1
    [ 1.813303] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2
    [ 1.813310] ACPI: Power Button [PWRB]
    [ 1.813368] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
    [ 1.813371] ACPI: Power Button [PWRF]
    [ 1.817850] wmi: Mapper loaded
    [ 1.855141] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
    [ 1.872038] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
    [ 1.872046] r8169 0000:06:00.0: can't disable ASPM; OS doesn't have ASPM control
    [ 1.877249] r8169 0000:06:00.0 eth0: RTL8168evl/8111evl at 0xffffc90000c7a000, 8c:89:a5:16:c4:7d, XID 0c900800 IRQ 32
    [ 1.877252] r8169 0000:06:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
    [ 1.880259] i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
    [ 1.907839] [drm] Initialized drm 1.1.0 20060810
    [ 1.910066] input: PC Speaker as /devices/platform/pcspkr/input/input5
    [ 1.911296] hidraw: raw HID events driver (C) Jiri Kosina
    [ 1.912890] snd_hda_intel 0000:01:00.1: Handle VGA-switcheroo audio client
    [ 1.913064] fuse init (API version 7.23)
    [ 1.914070] usblp 1-1.4:1.0: usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x04F9 pid 0x024A
    [ 1.914093] usbcore: registered new interface driver usblp
    [ 1.916048] AVX version of gcm_enc/dec engaged.
    [ 1.916050] AES CTR mode by8 optimization enabled
    [ 1.924639] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input6
    [ 1.925198] usbcore: registered new interface driver usbhid
    [ 1.925200] usbhid: USB HID core driver
    [ 1.926129] sound hdaudioC0D1: autoconfig: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
    [ 1.926132] sound hdaudioC0D1: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
    [ 1.926133] sound hdaudioC0D1: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
    [ 1.926134] sound hdaudioC0D1: mono: mono_out=0x0
    [ 1.926136] sound hdaudioC0D1: dig-out=0x11/0x1e
    [ 1.926137] sound hdaudioC0D1: inputs:
    [ 1.926139] sound hdaudioC0D1: Front Mic=0x19
    [ 1.926140] sound hdaudioC0D1: Rear Mic=0x18
    [ 1.926142] sound hdaudioC0D1: Line=0x1a
    [ 1.934672] iTCO_vendor_support: vendor-support=0
    [ 1.934826] [drm] radeon kernel modesetting enabled.
    [ 1.935110] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
    [ 1.935141] iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
    [ 1.935229] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
    [ 1.939587] r8169 0000:06:00.0 enp6s0: renamed from eth0
    [ 1.939661] gpio_ich: GPIO from 436 to 511 on gpio_ich
    [ 1.941371] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1d.0-1.2/input2
    [ 1.941824] AMD IOMMUv2 driver by Joerg Roedel <[email protected]>
    [ 1.941825] AMD IOMMUv2 functionality not available on this system
    [ 1.943447] CRAT table not found
    [ 1.943449] Finished initializing topology ret=0
    [ 1.943479] kfd kfd: Initialized module
    [ 1.943669] checking generic (c0000000 5b0000) vs hw (c0000000 10000000)
    [ 1.943670] fb: switching to radeondrmfb from VESA VGA
    [ 1.943685] Console: switching to colour dummy device 80x25
    [ 1.943797] random: nonblocking pool is initialized
    [ 1.943880] [drm] initializing kernel modesetting (CAYMAN 0x1002:0x6719 0x1787:0x2307).
    [ 1.943890] [drm] register mmio base: 0xFE620000
    [ 1.943891] [drm] register mmio size: 131072
    [ 1.943923] ATOM BIOS: CAYMAN
    [ 1.943974] radeon 0000:01:00.0: VRAM: 2048M 0x0000000000000000 - 0x000000007FFFFFFF (2048M used)
    [ 1.943975] radeon 0000:01:00.0: GTT: 1024M 0x0000000080000000 - 0x00000000BFFFFFFF
    [ 1.943977] [drm] Detected VRAM RAM=2048M, BAR=256M
    [ 1.943977] [drm] RAM width 256bits DDR
    [ 1.944037] [TTM] Zone kernel: Available graphics memory: 4075924 kiB
    [ 1.944038] [TTM] Zone dma32: Available graphics memory: 2097152 kiB
    [ 1.944039] [TTM] Initializing pool allocator
    [ 1.944043] [TTM] Initializing DMA pool allocator
    [ 1.944058] [drm] radeon: 2048M of VRAM memory ready
    [ 1.944059] [drm] radeon: 1024M of GTT memory ready.
    [ 1.944068] [drm] Loading CAYMAN Microcode
    [ 1.946470] input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
    [ 1.946562] input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
    [ 1.946609] input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
    [ 1.946674] input: HDA Intel PCH Line Out Front as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
    [ 1.946720] input: HDA Intel PCH Line Out Surround as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
    [ 1.946769] EXT4-fs (sdc2): mounted filesystem with ordered data mode. Opts: (null)
    [ 1.946769] input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
    [ 1.946809] input: HDA Intel PCH Line Out Side as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
    [ 1.946849] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
    [ 1.951281] [drm] Internal thermal controller with fan control
    [ 1.955166] [drm] radeon: dpm initialized
    [ 1.955974] [drm] GART: num cpu pages 262144, num gpu pages 262144
    [ 1.956619] input: Lite-On Technology Corp. Goldtouch USB Keyboard as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/0003:04CA:005B.0004/input/input15
    [ 1.957600] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
    [ 1.957733] intel_rapl: Found RAPL domain package
    [ 1.957736] intel_rapl: Found RAPL domain core
    [ 1.978933] [drm] PCIE GART of 1024M enabled (table at 0x0000000000274000).
    [ 1.979020] radeon 0000:01:00.0: WB enabled
    [ 1.979022] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff880234d8bc00
    [ 1.979798] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc90010f32118
    [ 1.979800] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff880234d8bc04
    [ 1.979801] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff880234d8bc08
    [ 1.979802] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff880234d8bc0c
    [ 1.979804] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff880234d8bc10
    [ 1.979805] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
    [ 1.979806] [drm] Driver supports precise vblank timestamp query.
    [ 1.979807] radeon 0000:01:00.0: radeon: MSI limited to 32-bit
    [ 1.979844] radeon 0000:01:00.0: radeon: using MSI.
    [ 1.980067] [drm] radeon: irq initialized.
    [ 1.998991] [drm] ring test on 0 succeeded in 2 usecs
    [ 1.998999] [drm] ring test on 3 succeeded in 4 usecs
    [ 1.999006] [drm] ring test on 4 succeeded in 4 usecs
    [ 2.010399] hid-generic 0003:04CA:005B.0004: input,hidraw1: USB HID v1.10 Keyboard [Lite-On Technology Corp. Goldtouch USB Keyboard] on usb-0000:00:1a.0-1.6/input0
    [ 2.012308] input: Lite-On Technology Corp. Goldtouch USB Keyboard as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.1/0003:04CA:005B.0005/input/input16
    [ 2.069928] input: Logitech M570 as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.2/4-1.2:1.2/0003:046D:C52B.0003/0003:046D:1028.0006/input/input17
    [ 2.080530] Adding 4194300k swap on /mnt/LinuxStorage/swap. Priority:-1 extents:4 across:4464636k FS
    [ 2.116506] hid-generic 0003:04CA:005B.0005: input,hiddev0,hidraw2: USB HID v1.10 Device [Lite-On Technology Corp. Goldtouch USB Keyboard] on usb-0000:00:1a.0-1.6/input1
    [ 2.116542] logitech-hidpp-device 0003:046D:1028.0006: input,hidraw3: USB HID v1.11 Mouse [Logitech M570] on usb-0000:00:1d.0-1.2:1
    [ 2.118008] mousedev: PS/2 mouse device common for all mice
    [ 2.175912] [drm] ring test on 5 succeeded in 2 usecs
    [ 2.175917] [drm] UVD initialized successfully.
    [ 2.176481] [drm] ib test on ring 0 succeeded in 0 usecs
    [ 2.176922] [drm] ib test on ring 3 succeeded in 0 usecs
    [ 2.177365] [drm] ib test on ring 4 succeeded in 0 usecs
    [ 2.328709] [drm] ib test on ring 5 succeeded
    [ 2.329264] [drm] Radeon Display Connectors
    [ 2.329265] [drm] Connector 0:
    [ 2.329266] [drm] DP-1
    [ 2.329267] [drm] HPD5
    [ 2.329268] [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c
    [ 2.329268] [drm] Encoders:
    [ 2.329269] [drm] DFP1: INTERNAL_UNIPHY2
    [ 2.329269] [drm] Connector 1:
    [ 2.329270] [drm] DP-2
    [ 2.329270] [drm] HPD4
    [ 2.329271] [drm] DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 0x644c
    [ 2.329271] [drm] Encoders:
    [ 2.329272] [drm] DFP2: INTERNAL_UNIPHY2
    [ 2.329272] [drm] Connector 2:
    [ 2.329273] [drm] HDMI-A-1
    [ 2.329273] [drm] HPD6
    [ 2.329274] [drm] DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 0x646c
    [ 2.329274] [drm] Encoders:
    [ 2.329275] [drm] DFP3: INTERNAL_UNIPHY1
    [ 2.329275] [drm] Connector 3:
    [ 2.329276] [drm] DVI-D-1
    [ 2.329276] [drm] HPD1
    [ 2.329277] [drm] DDC: 0x6450 0x6450 0x6454 0x6454 0x6458 0x6458 0x645c 0x645c
    [ 2.329277] [drm] Encoders:
    [ 2.329278] [drm] DFP4: INTERNAL_UNIPHY1
    [ 2.329278] [drm] Connector 4:
    [ 2.329279] [drm] DVI-I-1
    [ 2.329279] [drm] HPD3
    [ 2.329280] [drm] DDC: 0x6470 0x6470 0x6474 0x6474 0x6478 0x6478 0x647c 0x647c
    [ 2.329280] [drm] Encoders:
    [ 2.329281] [drm] DFP5: INTERNAL_UNIPHY
    [ 2.329282] [drm] CRT1: INTERNAL_KLDSCP_DAC1
    [ 2.408814] [drm] fb mappable at 0xC0475000
    [ 2.408816] [drm] vram apper at 0xC0000000
    [ 2.408816] [drm] size 8294400
    [ 2.408817] [drm] fb depth is 24
    [ 2.408818] [drm] pitch is 7680
    [ 2.408899] fbcon: radeondrmfb (fb0) is primary device
    [ 2.435470] Console: switching to colour frame buffer device 240x67
    [ 2.438497] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
    [ 2.438498] radeon 0000:01:00.0: registered panic notifier
    [ 2.449565] [drm] Initialized radeon 2.40.0 20080528 for 0000:01:00.0 on minor 0
    [ 2.459456] Switched to clocksource tsc
    [ 2.490495] cfg80211: Calling CRDA to update world regulatory domain
    [ 2.687833] r8169 0000:06:00.0 enp6s0: link down
    [ 2.687846] r8169 0000:06:00.0 enp6s0: link down
    [ 2.687870] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
    [ 20.764979] r8169 0000:06:00.0 enp6s0: link up
    [ 20.764992] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
    [ 256.173829] device-mapper: uevent: version 1.0.3
    [ 256.173991] device-mapper: ioctl: 4.29.0-ioctl (2014-10-28) initialised: [email protected]
    [ 256.713510] SGI XFS with ACLs, security attributes, realtime, no debug enabled
    [ 256.718933] JFS: nTxBlock = 8192, nTxLock = 65536
    [ 256.730155] ntfs: driver 2.1.31 [Flags: R/W MODULE].
    [ 256.800019] raid6: sse2x1 7801 MB/s
    [ 256.856622] raid6: sse2x2 11630 MB/s
    [ 256.913233] raid6: sse2x4 15648 MB/s
    [ 256.913234] raid6: using algorithm sse2x4 (15648 MB/s)
    [ 256.913235] raid6: using ssse3x2 recovery algorithm
    [ 256.913829] xor: automatically using best checksumming function:
    [ 256.946535] avx : 32756.400 MB/sec
    [ 256.954986] Btrfs loaded
    [ 603.210136] watchdog watchdog0: watchdog did not stop!
    [ 603.211033] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
    [ 603.244960] systemd-journald[149]: Received SIGTERM from PID 1 (systemd-shutdow).
    [ 603.321496] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
    [ 603.325328] systemd-shutdown[1]: Hardware watchdog 'iTCO_wdt', version 0
    [ 603.325462] systemd-shutdown[1]: Unmounting file systems.
    [ 603.393079] EXT4-fs (sdb1): re-mounted. Opts: (null)
    [ 603.402416] EXT4-fs (sdb1): re-mounted. Opts: (null)
    [ 603.402433] systemd-shutdown[1]: All filesystems unmounted.
    [ 603.402438] systemd-shutdown[1]: Deactivating swaps.
    [ 603.402507] systemd-shutdown[1]: All swaps deactivated.
    [ 603.402511] systemd-shutdown[1]: Detaching loop devices.
    [ 603.403097] systemd-shutdown[1]: All loop devices detached.
    [ 603.403101] systemd-shutdown[1]: Detaching DM devices.
    [ 603.403156] systemd-shutdown[1]: All DM devices detached.
    [ 603.412388] EXT4-fs (sdb1): re-mounted. Opts: data=ordered
    Would appreciate some input regarding this. Thanks!
    EDIT: This is on gnome 3.16. Not sure if that matters.
    Last edited by devrepublic (2015-05-13 03:24:19)

    ksu wrote:Thanks alot for the input guys. Since I want to start from scratch anyways I'll definitively dig deeper into the subject. BTRFS snapshot feature and RAID1 by simply mirroring two partitions sound awesome, and the subvolume feature seems to be exactly what I need for my USB setup, giving me alot of flexibility. But if there are really that many reports of random data loss then I'll also do some research into that direction to see what this is all about. I admit I'm a linux noob, but it's a lot of fun to learn all this stuff.
    Be sure to read this: https://btrfs.wiki.kernel.org/index.php/Gotchas
    From my own experience, I can say that:
    1. I've never had an issue nor data loss with BTRFS RAID1 root partition on a single disk (other than the first issue on the above list).
    2. I had recurring problems with BTRFS RAID1 non-root partition on a single disk not being able to mount (had to reboot random number of times to get it to mount). However, I suspect this was caused not just by BTRFS but the combination of BTRFS+LVM+dmcrypt which is a rather complex and unusual setup. I had somewhat similar issue with ZFS.
    3. I had BTRFS checkdisk report strange, non-critical, unfixable errors on my non-raid BTRFS root partition, but it never corrupted or lost any data. I simply copied the data to another partition, recreated the root partition and all was fine again.
    4. The last time I lost data on a single partition because of BTRFS was 17 months ago. The last time BTRFS snapshot saved me from losing data was yesterday.
    5. I migrated from BTRFS to ZFS for my backup server and will possibly do so for my work machines. ZFS is more elegant, mature and I have seen no complaints of losing data because of it. However, ZFS is complicated and somewhat restrictive to setup for a data partition, and many times more difficult to setup as root partition. I would not consider it for a non-permanent USB installation.
    6. What we committed here is a massive thread hijacking.
    Last edited by Lockheed (2015-04-24 05:27:51)

  • A failsafe backup mechanism for pacman

    would be nice to have!
    I just did pacman -Syu and once again it broke my system. This time I'm no longer able to access 3d-acceleration via dedicated nvidia board. I've already made an appropriate thread in 'Kernel/Hardware', but I also wanted to suggest this, by copy/pasting the "PPS" appendix I wrote here:
    Regarding: System breaks in one way or the other after pacman -Syu (happened to me last 5 times out of 15, worst case was I couldn't even start Slim or X):
    All of this tinkering is always so exhausting and annoying, it'd be really nice if Arch/pacman could somehow add an easy to use rollback mechanism for cases like this where your system becomes unusable. Some sort of automatic backup of exactly the files affected by doing the pacman -Syu thing (eg linux kernel). Just so you don't have to spend hours of random testing/asking/hoping to sort things out but can go back to where you started in one click/command. For people who want to use Linux to get things done, as opposed to those who love the actual tinkering.
    I'm not sure how much longer I will have the spare time available to try and fix it myself and everything, there might come a time where I will have to either drop Arch or just never do pacman -Syu again, if I have too much to do with work and just cannot afford breaking my system with what was supposed to be "updating" anymore
    Last edited by Jindur (2013-04-26 11:52:22)

    valr wrote:
    ...and because pacman can't know all the config files that have been modified my users (some files are tracked, others not) then pacman is maybe not the tool for that.
    Have you checked at options like filesystem snapshotting or versioning file system ?
    Has any arch user ever used such tools as "rollback feature" ?
    I would be interested to know.
    In the past I have successfully used btrfs snapshots as a rollback.
    Being careful with /boot it is possible to boot anyone of the snapshots independently; but to do so one also has to choose between keeping the whole /home in the snapshot or taking a copy of user config files.
    I had this setup during one of the big changes to glibc or filesystem: I had the opportunity to run "pacman -Syu --force" breaking the primary system; going back to the previous snapshot worked fine and was easier than recovering from the errors.
    I do not have it anymore after I managed to crash the whole filesystem (stupid typo in grub while I was configuring the swap partition for hibernation).
    At the end I decided it is not worth for me. Now I just update carefully and if I have enough time to recover from an eventual failure.
    On the other hand, if you are willing to use btrfs, it is not much harder that installing on an usual ext4 and it will be a fun learning experience.

  • My iTunes has multiple phones and computers with similar names associated with it. How do I know which are the right ones?

    I'm trying to clean up my iTunes account and I see several of the same phone or computer listed as authorized users. How do I figure out which are the correct phones/computers?

    Alvin777 wrote:
    Hi. I'd like to delete the Snow Leopard Snapshots in my Time Machine backup drive because it won't work with Lion
    I'm not sure what you mean . . . what won't work with Lion?  It sounds like it did do some backups.
    Is there a way or an app to know which are Lion snapshots? 
    There is a way, but it's rather cumbersome.  You have to start selecting a full system restore; there's a window showing all of the backups and the version of OSX. 
    Is there an app I could use to manage the snapshots if manually deleting them will cause problems and side effects later.
    It's best to use the Time Machine "Star Wars" display to delete backups, but you really shouldn't have to.  Let's figure out what's wrong first.

Maybe you are looking for

  • Passing JavaScript value to Jsp

    Hi, Any idea how to pass a value from javascript to jsp page when the page gets load on browser. I use below code but an event is require to pass the value. Is there any code that pass automatically the value from javascript to jsp. <html> <head> <ti

  • OBIEE 11.1.1.6 Help needed to resolve a user requirement for an analysis

    Hi all, I need to create a pivot table like this: Show a calculated measure VALUE / QUANTITY by dimension1 (on rows) and year & month (on columns). Add a grand total on year. Add a calculated item that shows the difference between grand total on year

  • After watching 25 mn, it stops "Could not load movie"

    I rented a movie on my iPad from iTunes Store. After 25 mn of watching it stops and it says "could not load movie" then it has been fully downloaded. The Apple assistance says "if your download was interrupted 1/ From the Home screen, tap the iTunes

  • Flash Update Issue

    I have just dowloaded the latest Flash update (11.3.300.262) but keep getting an assertion failed message. My pc is running windows vista and the browser is Firefox. How can I fix this please?

  • SAP B1 query generator problem

    Experts, i have created one Stored Procedure and want to execute from SAP B1 query manager, but it gives error like 1). [Microsoft][SQL Server Native Client 10.0][SQL Server]Warning: Null value is eliminated by an aggregate or other SET operation.  '