Re: [CentOS] new laptop: DVD or Blu-ray
On 09/13/15, Always Learning wrote: - Quoted text --- Where does one obtain the RPM for Centos 5 and 6, please ? - End quote See: vault.centos.org ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rsync question
On 09/10/15, Robert Moskowitz wrote: --- Quoted text -- SSh is not parsing the port the way http does, it seems: $ rsync -ah --stats root@192.168.129.2:613:/etc/dhcp/ /home/rgm/data/htt/httnet/homebase/new/dhcp ssh: connect to host 192.168.129.2 port 22: No route to host rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.1] The reason why I change my SSH port is a simple way to keep port knocker robots away. Different hosts use different ports... -- End quote Oh, right, so you either need to put that in your .ssh/config file or use -e 'ssh -p 613' on the rsync command. The config file should look like this: Host 192.168.129.2 Port 613 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rsync question
On 09/10/15, Robert Moskowitz wrote: Quoted text I just tried the following: rsync -ah --stats "ssh -p613 -l root" 192.168.192.2:/root/samba.PDC/ /home/rgm/data/htt/httnet/homebase/new/root/ And it failed with: Unexpected remote arg: 192.168.192.2:/root/samba.PDC/ rsync error: syntax or usage error (code 1) at main.c(1330) [sender=3.1.1] I tried again with: rsync -ah --stats -e "ssh -p613 -l root" 192.168.192.2:/root/samba.PDC/ /home/rgm/data/htt/httnet/homebase/new/root/ and it worked. This is what I read from the manpage, that "-e" is needed for the ssh command. - End Quote -- Try this: rsync -ah --stats 192.168.192.2:/root/samba.PDC/ /home/rgm/data/htt/httnet/homebase/new/root/ ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rsync question
On 09/10/15, C Linus Hicks wrote: On 09/10/15, Robert Moskowitz wrote: Quoted text Try this: rsync -ah --stats 192.168.192.2:/root/samba.PDC/ /home/rgm/data/htt/httnet/homebase/new/root/ - End Quote -- Sorry, I was too fast, not paying attention, you want this I believe: rsync -ah --stats root@192.168.192.2:/root/samba.PDC/ /home/rgm/data/htt/httnet/homebase/new/root/ That will use the default port on the remote host, you can override that without specifying the -e if required using -p . ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.1 install with Areca arc-1224
On 07/06/15, g wrote: you might try verifying that system you are getting error message on has a good cd/dvd drive. burn another dvd at at least 4 speeds slower. if runs ok, bad drive. if still fails, bad drive. another way you can check is to pull iso on system you are having problem with and burn dvd. if you get error, get a new drive. Above quoted When I md5sum the DVD on the system I burned it on, it matches. When I md5sum it on another system, it matches. When I md5sum it on the system I am trying to install, it comes up with a different answer. I'm getting a new DVD drive. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.1 install with Areca arc-1224
On 07/05/2015 09:17 AM, lin...@verizon.net wrote: Someone please tell me what I did to screw this thing up so badly. On 07/05/15, Gordon Messmergordon.mess...@gmail.com wrote: Have you looked at the log files in /mnt/sysimage/root/? - Quoting broken in this mailer So I looked in /mnt/sysimage/var/log/anaconda and found this in anaconda.packaging.log: - cut - 02:40:53,109 DEBUG packaging: Installing abrt-dbus (684/1349) 02:40:53,125 DEBUG packaging: Installing flite (685/1349) 02:40:54,291 DEBUG packaging: Traceback (most recent call last): 02:40:54,291 DEBUG packaging: File /usr/libexec/anaconda/anaconda-yum, line 220, in callback 02:40:54,292 DEBUG packaging: return func(amount, total, key, data) 02:40:54,292 DEBUG packaging: File /usr/libexec/anaconda/anaconda-yum, line 342, in inst_open_file 02:40:54,292 DEBUG packaging: os.unlink(txmbr.po.localPkg()) 02:40:54,292 DEBUG packaging: OSError: [Errno 30] Read-only file system: '/run/install/repo/Packages/flite-1.3-22.el7.x86_64.rpm' 02:40:54,292 DEBUG packaging: FATAL ERROR: python callback bound method RPMCallback.callback of __main__.RPMCallback object at 0x7fa4569d1a10 failed, aborting! 02:40:54,393 INFO packaging: start rpm scriptlet logs 02:40:54,393 INFO packaging: warning: filesystem-3.2-18.el7.x86_64: Header V3 RSA/SHA256 Signature, key ID f4a80eb5: NOKEY 02:40:54,393 INFO packaging: libgcc-4.8.3-9.el7.x86_64 (1/1349) 02:40:54,393 INFO packaging: fontpackages-filesystem-1.44-8.el7.noarch (2/1349) 02:40:54,393 INFO packaging: 1:control-center-filesystem-3.8.6-18.el7.x86_64 (3/1349) - cut - The path it is complaining is a read-only filesystem is the installation DVD. If my interpretation is correct, it appears to be attempting to delete a file on the DVD. Is there some issue with installing flite or is something else going on? When I searched there was a bug opened on a similar issue, but the person had a RAID array failure and the only error I see in the anaconda.storage.log is this: -- cut 02:24:19,798 DEBUG blivet: parsing /mnt/sysimage/etc/blkid/blkid.tab 02:24:19,799 INFO blivet: IGNORED: Caught exception, continuing. 02:24:19,799 INFO blivet: IGNORED: Problem description: error parsing blkid.tab 02:24:19,800 INFO blivet: IGNORED: Begin exception details. 02:24:19,800 INFO blivet: IGNORED: Traceback (most recent call last): 02:24:19,800 INFO blivet: IGNORED: File /usr/lib/python2.7/site-packages/blivet/__init__.py, line 3227, in parseFSTab 02:24:19,800 INFO blivet: IGNORED: blkidTab.parse() 02:24:19,800 INFO blivet: IGNORED: File /usr/lib/python2.7/site-packages/blivet/__init__.py, line 2282, in parse 02:24:19,800 INFO blivet: IGNORED: with open(path) as f: 02:24:19,800 INFO blivet: IGNORED: IOError: [Errno 2] No such file or directory: '/mnt/sysimage/etc/blkid/blkid.tab' 02:24:19,800 INFO blivet: IGNORED: End exception details. -- cut - Which doesn't appear to be fatal. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.1 install with Areca arc-1224
On 07/05/15, Gordon Messmer wrote: anaconda will try to delete an rpm file if it gets an IOError. Your media may be corrupt. Check that first. - Above quoted - No such luck. On the system where I'm doing the install, I used dd to read the entire DVD and also copied every .rpm to /dev/null and didn't get any I/O errors. What next? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.1 install with Areca arc-1224
On 07/05/15, Gordon Messmer wrote: That's not the same as checking the media for corruption. You may be able to read all of the files, but if the data is corrupt, rpm may throw and IOError. So, the next thing to do is check your media. The DVD should offer to do that first when you boot from it. -- Above quoted Booted the DVD again, took the default. It got to 76.2% then told me: The media check is complete. The result is: FAIL. It is not recommended to use this media. [FAILED] Failed to start media check on /dev/sr0. See 'systemctl status checkisomd5@-dev-sr0.service' for details. dracut-initqueue[681]: Job for checkisomd5@-dev-sr0.service failed. See 'systemctl status checkisomd5@-dev-sr0.service' and 'journalctl -xn' for details. [ 243.972119] dracut: FATAL: CD check failed! [ 243.972141] dracut: Refusing to continue Could not unmount /run/install/repo: Device or resource busy [ 245.127417] System halted. Ran the check again, same thing. Took that DVD back to the machine I burned it on, downloaded the MD5SUM from one of the mirrors and checked the file I downloaded. That checks. Used cmp to compare the .iso file to the image on the DVD, they match, the DVD is good. Hmm, what gives. Burned another DVD and verified the burned image matches the .iso file. Took the new DVD to the machine I'm doing the install on and ran the check again. OMG, it did the same thing at 76.2%. Now I'm thinking, wait, it says Failed to start media check is that a poorly worded message or does it really mean what it says? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problems after update to 5.5
On Mon, 2010-05-17 at 01:20 -0400, JohnS wrote: I am just wondering if any of you guys with the udev hang problem have tried: rpm -e the new kernel? Then try to reinstall it via yum install. You should delete the new kernel from /var/cache/yum first. Just a point in why I say that is I have seen several machines that have yummed corrupt packages and bad repo metadata. After pegging yum to pull from a distinct mirror the problem has gone away. John How about this: I downloaded the new kernel rpm again manually then used rpm2cpio to load the files into a work directory then ran this script: $ rpm -qlp ../kernel-2.6.18-194.3.1.el5.x86_64.rpm | while read rl do rstr=$(cmp $rl .$rl 21) rc=$? if (( rc != 0 )); then echo $rstr | grep -v Is a directory /dev/null rc=$? if (( rc == 0 )); then echo Error: $rstr fi fi done Error: cmp: ./boot/initrd-2.6.18-194.3.1.el5.img: No such file or directory Error: cmp: ./lib/modules/2.6.18-194.3.1.el5/build: No such file or directory Error: cmp: ./lib/modules/2.6.18-194.3.1.el5/source: No such file or directory ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problems after update to 5.5
On Sat, 2010-05-15 at 12:27 +0100, Colin Coles wrote: Hi, I have updated 8 machines so far and 2 are refusing to boot on 2.6.18-194.3.1.el5 kernel, they just hang at: 'Starting udev:' but when I revert to 2.6.18-164.15.1.el5 kernel they boot fine. Any pointers? I just updated a machine and also got a hang at udev. When I revert to kernel 2.6.18-164 it works fine. It appears to be a hard hang. Caps lock and num lock have no effect and I have to hit the reset button. I tried increasing udev log level to debug and it did not hang. I reduced the log level to info and it still did not hang. However, when I start X, esd seems to get stuck in a loop on a short segment of audio. If I kill esd, the desktop will finish initializing. Logging out of X also hung, but killing X manually worked. I have reverted to the old kernel. Linus ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] xfs_repair doesn't fix sb versionnum missing attr
On Fri, 2010-02-12 at 07:02 -0500, Brent L. Bates wrote: The first question is did you unmount the file system first before doing both the xfs_check and xfs_repair? A file system should not be mounted while doing either of these. xfs_check will give false failures if it is run while the file system is mounted. If everything was unmounted while you used these utilities, then may be the disk is failing. At the moment, I don't know what else to check. The filesystem was not mounted at the time I ran either xfs_check or xfs_repair, and the disk is not failing. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] xfs_repair doesn't fix sb versionnum missing attr
I run: xfs_check /dev/sdc10 And it reports: sb versionnum missing attr bit 10 Then I run: xfs_repair /dev/sdc10 And it reports output from 7 phases and done. Again I run: xfs_check /dev/sdc10 And it reports: sb versionnum missing attr bit 10 Is this how it's supposed to work? Thanks for any help. Linus ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Building xfsprogs can't find valid UUID library
On CentOS 5.3 x86_64, I'm trying to build xfsprogs-2.9.4-1.el5.centos.x86_64 with -ggdb so I can use it with gdb and examine the data structures when using xfs_db. I've installed the src rpm as a non-root user and when I run rpmbuild -bc during the ./configure I get the error: . . . checking uuid.h usability... no checking uuid.h presence... no checking for uuid.h... no checking sys/uuid.h usability... no checking sys/uuid.h presence... no checking for sys/uuid.h... no checking uuid/uuid.h usability... yes checking uuid/uuid.h presence... yes checking for uuid/uuid.h... yes checking for uuid_compare... no checking for uuid_compare in -luuid... no FATAL ERROR: could not find a valid UUID library. Install the Universally Unique Identifiers library package. error: Bad exit status from /var/tmp/rpm-tmp.42904 (%build) However, I found that /lib64/libuuid.so.1.2 (provided by e2fsprogs-libs-1.39-20.el5.x86_64) does exist and using nm -D shows an entry point for uuid_compare: 00385a6015e0 T uuid_compare Then I did: strings ld.so.cache | grep uuid libuuid.so.1 /lib64/libuuid.so.1 libuuid.so.1 /lib/libuuid.so.1 libuuid.so /usr/lib/libuuid.so And /lib64/libuuid.so.1 is a symbolic link to /lib64/libuuid.so.1.2. The only hit on Google that looked interesting was from 2006: http://oss.sgi.com/archives/xfs/2006-03/msg00425.html Can anybody tell me what's going wrong and how to fix it? Thanks for your help. Linus ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Building xfsprogs can't find valid UUID library
On Sat, 2009-12-05 at 12:29 -0800, Akemi Yagi wrote: On Sat, Dec 5, 2009 at 10:43 AM, C Linus Hicks lin...@verizon.net wrote: On CentOS 5.3 x86_64, I'm trying to build xfsprogs-2.9.4-1.el5.centos.x86_64 with -ggdb so I can use it with gdb and examine the data structures when using xfs_db. I've installed the src rpm as a non-root user and when I run rpmbuild -bc during the ./configure I get the error: checking for uuid.h... no FATAL ERROR: could not find a valid UUID library. Install the Universally Unique Identifiers library package. error: Bad exit status from /var/tmp/rpm-tmp.42904 (%build) You might want to try installing e2fsprogs-devel and see how it goes. That did it. I can't imagine doing this on purpose, but I had the i386 e2fsprogs-devel installed but not the x86_64. rpm -qa e2fsprogs* e2fsprogs-1.39-20.el5.x86_64 e2fsprogs-devel-1.39-20.el5.i386 e2fsprogs-libs-1.39-20.el5.i386 e2fsprogs-libs-1.39-20.el5.x86_64 Thanks for your help. Linus ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Possible to run iscsi-target and initiator on same server?
On Sun, 2009-10-11 at 17:14 -0400, C Linus Hicks wrote:
strace output:
--
- Cut a bunch of lines
socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 6
socket(PF_NETLINK, SOCK_RAW, 0) = 7
bind(7, {sa_family=AF_NETLINK, pid=0, groups=}, 12) = 0
getsockname(7, {sa_family=AF_NETLINK, pid=28308, groups=},
[137438953484]) = 0
sendto(7, \24\0\0\0\22\0\1\3\365\201\321J\0\0\0\0\0\0\0\0, 20, 0,
{sa_family=AF_NETLINK, pid=0, groups=}, 12) = 20
recvmsg(7, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{\370\0\0\0\20\0\2\0\365\201\321J\224n\0\0\0\0\4\3\1\0\0\0I\0\1\0\0\0\0\0...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 1004
recvmsg(7, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{\24\0\0\0\3\0\2\0\365\201\321J\224n\0\0\0\0\0\0\1\0\0\0I\0\1\0\0\0\0\0...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 20
sendto(7, \24\0\0\0\26\0\1\3\366\201\321J\0\0\0\0\0\0\0\0, 20, 0,
{sa_family=AF_NETLINK, pid=0, groups=}, 12) = 20
recvmsg(7, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{\0\0\0\24\0\2\0\366\201\321J\224n\0\0\2\10\200\376\1\0\0\0\10\0\1\0\177\0\0\1...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 196
recvmsg(7, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{@\0\0\0\24\0\2\0\366\201\321J\224n\0\0\n\200\200\376\1\0\0\0\24\0\1\0\0\0\0\0...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 192
recvmsg(7, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{\24\0\0\0\3\0\2\0\366\201\321J\224n\0\0\0\0\0\0\1\0\0\0\24\0\1\0\0\0\0\0...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 20
close(7)= 0
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 7
ioctl(7, SIOCGIFHWADDR, {ifr_name=lo, ifr_hwaddr=00:00:00:00:00:00}) = 0
ioctl(7, SIOCGIFHWADDR, {ifr_name=eth2, ifr_hwaddr=00:1d:92:b4:50:6e}) = 0
close(7)= 0
setsockopt(6, SOL_SOCKET, SO_BINDTODEVICE, eth2\0, 5) = 0
setsockopt(6, SOL_TCP, TCP_NODELAY, [1], 4) = 0
setsockopt(6, SOL_SOCKET, SO_RCVBUF, [524288], 4) = 0
getsockopt(6, SOL_SOCKET, SO_RCVBUF, [4296015872], [4]) = 0
setsockopt(6, SOL_SOCKET, SO_SNDBUF, [524288], 4) = 0
getsockopt(6, SOL_SOCKET, SO_SNDBUF, [4296015872], [4]) = 0
fcntl(6, F_GETFL) = 0x2 (flags O_RDWR)
fcntl(6, F_SETFL, O_RDWR|O_NONBLOCK)= 0
connect(6, {sa_family=AF_INET, sin_port=htons(3260),
sin_addr=inet_addr(10.200.1.6)}, 128) = -1 EINPROGRESS (Operation now in
progress)
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=0, events=0}], 3,
250) = 0 (Timeout)
poll([{fd=6, events=POLLOUT}], 1, 1)= 0 (Timeout)
- Cut a bunch more lines
I believe the problem is evident from the strace. He binds the socket to
eth2 based on querying the MAC address. That means he will only receive
packets on eth2 and since the network layer has determined that origin
and destination are the same, it's passing the traffic across the
loopback interface. Thus he will never see a response from the ietd
daemon.
If my interpretation is correct, then the two possibilities I see are
that this is either a design restriction or a bug.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Possible to run iscsi-target and initiator on same server?
On Sun, 2009-10-11 at 17:14 -0400, C Linus Hicks wrote:
strace output:
--
--- a bunch of lines cut ---
socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 6
socket(PF_NETLINK, SOCK_RAW, 0) = 7
bind(7, {sa_family=AF_NETLINK, pid=0, groups=}, 12) = 0
getsockname(7, {sa_family=AF_NETLINK, pid=28308, groups=},
[137438953484]) = 0
sendto(7, \24\0\0\0\22\0\1\3\365\201\321J\0\0\0\0\0\0\0\0, 20, 0,
{sa_family=AF_NETLINK, pid=0, groups=}, 12) = 20
recvmsg(7, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{\370\0\0\0\20\0\2\0\365\201\321J\224n\0\0\0\0\4\3\1\0\0\0I\0\1\0\0\0\0\0...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 1004
recvmsg(7, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{\24\0\0\0\3\0\2\0\365\201\321J\224n\0\0\0\0\0\0\1\0\0\0I\0\1\0\0\0\0\0...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 20
sendto(7, \24\0\0\0\26\0\1\3\366\201\321J\0\0\0\0\0\0\0\0, 20, 0,
{sa_family=AF_NETLINK, pid=0, groups=}, 12) = 20
recvmsg(7, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{\0\0\0\24\0\2\0\366\201\321J\224n\0\0\2\10\200\376\1\0\0\0\10\0\1\0\177\0\0\1...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 196
recvmsg(7, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{@\0\0\0\24\0\2\0\366\201\321J\224n\0\0\n\200\200\376\1\0\0\0\24\0\1\0\0\0\0\0...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 192
recvmsg(7, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{\24\0\0\0\3\0\2\0\366\201\321J\224n\0\0\0\0\0\0\1\0\0\0\24\0\1\0\0\0\0\0...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 20
close(7)= 0
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 7
ioctl(7, SIOCGIFHWADDR, {ifr_name=lo, ifr_hwaddr=00:00:00:00:00:00}) = 0
ioctl(7, SIOCGIFHWADDR, {ifr_name=eth2, ifr_hwaddr=00:1d:92:b4:50:6e}) = 0
close(7)= 0
setsockopt(6, SOL_SOCKET, SO_BINDTODEVICE, eth2\0, 5) = 0
setsockopt(6, SOL_TCP, TCP_NODELAY, [1], 4) = 0
setsockopt(6, SOL_SOCKET, SO_RCVBUF, [524288], 4) = 0
getsockopt(6, SOL_SOCKET, SO_RCVBUF, [4296015872], [4]) = 0
setsockopt(6, SOL_SOCKET, SO_SNDBUF, [524288], 4) = 0
getsockopt(6, SOL_SOCKET, SO_SNDBUF, [4296015872], [4]) = 0
fcntl(6, F_GETFL) = 0x2 (flags O_RDWR)
fcntl(6, F_SETFL, O_RDWR|O_NONBLOCK)= 0
connect(6, {sa_family=AF_INET, sin_port=htons(3260),
sin_addr=inet_addr(10.200.1.6)}, 128) = -1 EINPROGRESS (Operation now in
progress)
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=0, events=0}], 3,
250) = 0 (Timeout)
poll([{fd=6, events=POLLOUT}], 1, 1)= 0 (Timeout)
--- a bunch more lines cut ---
So by looking in the code, it will avoid binding to the device under
default conditions. I removed the MAC address from the iface0 file and
the login works.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Possible to run iscsi-target and initiator on same server?
On Sun, 2009-10-11 at 12:36 -0400, Ross Walker wrote: What does the ietd.conf, initiators.allow and targets.allow look like? What is your network setup? Are you using a vif on the loopback? There's no VIF on loopback. The machine running iet has two NICs, the private interconnect should not be playing a role. It's IP address is 10.200.2.2/24 while the local subnet is 10.200.1.0/24 and the iet machine is IP address 10.200.1.6. ietd.conf -- Target iqn.2009-10.net.linush:storage.disk1.sys1.asmdg Lun 0 Path=/dev/sdb,Type=blockio,ScsiId=asmdg,ScsiSN=dg0 HeaderDigest None DataDigest None MaxConnections 1 InitialR2T No ImmediateData Yes MaxRecvDataSegmentLength 262144 MaxXmitDataSegmentLength 262144 MaxBurstLength 524288 FirstBurstLength 262144 MaxOutstandingR2T 8 DataPDUInOrder Yes DataSequenceInOrder Yes ErrorRecoveryLevel 0 initiators.allow ALL 10.200.1.0/24 targets.allow ALL 10.200.1.0/24 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Possible to run iscsi-target and initiator on same server?
On Sun, 2009-10-11 at 15:13 -0400, C Linus Hicks wrote:
There's no VIF on loopback. The machine running iet has two NICs, the
private interconnect should not be playing a role. It's IP address is
10.200.2.2/24 while the local subnet is 10.200.1.0/24 and the iet
machine is IP address 10.200.1.6.
From running strace on the iscsid daemon, it appears to be taking what
looks to me like an unexpected error. In the text below, look for the
first series of poll system calls. Just after that section is where I
initiate the iscsiadm login command. Then about 100 lines later on, it
issues a connect call that returns -1 EINPROGRESS (Operation now in
progress). Then it goes back to polling, this time on two sockets
including the one it just tried to connect on. In a little while it
probably reaches the retry limit and closes that socket. It makes
another connect attempt that fails with the same error. There are a
total of five connect attempts, but I have cut out some of the repeated
text.
strace output:
--
execve(/sbin/iscsid, [iscsid, -f, -c, /etc/iscsi/iscsid.conf], [/* 29
vars */]) = 0
brk(0) = 0x28de000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x2ac7443dc000
uname({sys=Linux, node=lh6.linush.net, ...}) = 0
access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or directory)
open(/etc/ld.so.cache, O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=161740, ...}) = 0
mmap(NULL, 161740, PROT_READ, MAP_PRIVATE, 3, 0) = 0x2ac7443dd000
close(3)= 0
open(/lib64/libc.so.6, O_RDONLY) = 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0p\332\341_2\0\0\0...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1713096, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x2ac744405000
mmap(0x325fe0, 3494168, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0x325fe0
mprotect(0x325ff4c000, 2097152, PROT_NONE) = 0
mmap(0x326014c000, 20480, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x14c000) = 0x326014c000
mmap(0x3260151000, 16664, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x3260151000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x2ac744406000
arch_prctl(ARCH_SET_FS, 0x2ac744406250) = 0
mprotect(0x326014c000, 16384, PROT_READ) = 0
mprotect(0x325f01b000, 4096, PROT_READ) = 0
munmap(0x2ac7443dd000, 161740) = 0
rt_sigaction(SIGINT, {0x41ec00, [], SA_RESTORER, 0x325fe30280}, {SIG_DFL, [],
0}, 8) = 0
rt_sigaction(SIGPIPE, {0x41ec00, [], SA_RESTORER, 0x325fe30280}, {SIG_DFL, [],
0}, 8) = 0
rt_sigaction(SIGTERM, {0x41ec00, [], SA_RESTORER, 0x325fe30280}, {SIG_DFL, [],
0}, 8) = 0
brk(0) = 0x28de000
brk(0x28ff000) = 0x28ff000
open(/sys/module/scsi_transport_iscsi/version, O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x2ac7443dd000
read(3, 2.0-871\n, 4096) = 8
close(3)= 0
munmap(0x2ac7443dd000, 4096)= 0
write(2, iscsid: , 8iscsid: ) = 8
write(2, transport class version 2.0-871, 55transport class version
2.0-871. iscsid version 2.0-868) = 55
write(2, \n, 1
) = 1
umask(0177) = 022
socket(PF_FILE, SOCK_STREAM, 0) = 3
bind(3, {sa_family=AF_FILE, path=@ISCSIADM_ABSTRACT_NAMESPACE}, 110) = 0
listen(3, 32) = 0
socket(PF_NETLINK, SOCK_RAW, 8) = 4
getpid()= 28308
bind(4, {sa_family=AF_NETLINK, pid=28308, groups=0001}, 12) = 0
open(/etc/iscsi/initiatorname.iscsi, O_RDONLY) = 5
fstat(5, {st_mode=S_IFREG|0644, st_size=50, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x2ac7443dd000
read(5, InitiatorName=iqn.2009-10.net.li..., 4096) = 50
read(5, , 4096) = 0
close(5)= 0
munmap(0x2ac7443dd000, 4096)= 0
open(/etc/iscsi/initiatorname.iscsi, O_RDONLY) = 5
fstat(5, {st_mode=S_IFREG|0644, st_size=50, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x2ac7443dd000
read(5, InitiatorName=iqn.2009-10.net.li..., 4096) = 50
read(5, , 4096) = 0
close(5)= 0
munmap(0x2ac7443dd000, 4096)= 0
uname({sys=Linux, node=lh6.linush.net, ...}) = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x2ac7444062e0) = 28309
getpriority(PRIO_PROCESS, 0)= 20
setpriority(PRIO_PROCESS, 0, 4294967286) = 0
getpriority(PRIO_PROCESS, 0)= 30
open(/proc/28308/oom_adj, O_WRONLY) = 5
Re: [CentOS] Possible to run iscsi-target and initiator on same server?
On Sun, 2009-10-11 at 17:43 -0400, Ross Walker wrote: I'm a little confused now, you are running IET and open-iscsi on the same host, buy using an external interface for the connection between the two instead of the loopback? You would get much better throughput on the loopback. Sure, that makes sense. Given that /var/lib/iscsi/ifaces/iface0 seems to require a MAC address, I did not think there was a way to do that. Perhaps you could enlighten me... ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Possible to run iscsi-target and initiator on same server?
On Sun, 2009-10-11 at 17:51 -0400, Ross Walker wrote: I don't know much about open-iscsi, just IET and the best way to diagnose iSCSI problems is via tcpdump and wireshark not strace. Is the iscsi-target service running? [r...@lh6 iscsi]# netstat -nlp | grep 3260 tcp0 0 0.0.0.0:32600.0.0.0:* LISTEN 16475/ietd tcp0 0 :::3260 :::* LISTEN 16475/ietd ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Possible to run iscsi-target and initiator on same server?
On Sun, 2009-10-11 at 23:26 -0400, Ross Walker wrote: Can you send a short tcpdump between initiator and target during discovery/login? Sure. Note that all this traffic is on the lo interface. The discovery command and tcpdump output: [r...@lh6 ~]# iscsiadm -m discovery -t st -p 10.200.1.6:3260 -P 1 Target: iqn.2009-10.net.linush:storage.disk1.sys1.asmdg Portal: 10.200.1.6:3260,1 Iface Name: iface0 [r...@lh6 iscsi]# tcpdump -i lo -n -vv 00:03:04.584545 IP (tos 0x0, ttl 64, id 55720, offset 0, flags [DF], proto: TCP (6), length: 60) 10.200.1.6.20331 10.200.1.6.iscsi-target: S, cksum 0x4851 (correct), 3727115272:3727115272(0) win 32792 mss 16396,sackOK,timestamp 296394144 0,nop,wscale 8 00:03:04.584547 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: TCP (6), length: 60) 10.200.1.6.iscsi-target 10.200.1.6.20331: S, cksum 0x6389 (correct), 3721615280:3721615280(0) ack 3727115273 win 32768 mss 16396,sackOK,timestamp 296394144 296394144,nop,wscale 8 00:03:04.584559 IP (tos 0x0, ttl 64, id 55721, offset 0, flags [DF], proto: TCP (6), length: 52) 10.200.1.6.20331 10.200.1.6.iscsi-target: ., cksum 0x4c2e (correct), 1:1(0) ack 1 win 129 nop,nop,timestamp 296394144 296394144 00:03:04.584608 IP (tos 0x0, ttl 64, id 55722, offset 0, flags [DF], proto: TCP (6), length: 100) 10.200.1.6.20331 10.200.1.6.iscsi-target: P 1:49(48) ack 1 win 129 nop,nop,timestamp 296394145 296394144 00:03:04.584615 IP (tos 0x0, ttl 64, id 51728, offset 0, flags [DF], proto: TCP (6), length: 52) 10.200.1.6.iscsi-target 10.200.1.6.20331: ., cksum 0x4bfd (correct), 1:1(0) ack 49 win 128 nop,nop,timestamp 296394145 296394145 00:03:04.584623 IP (tos 0x0, ttl 64, id 55723, offset 0, flags [DF], proto: TCP (6), length: 304) 10.200.1.6.20331 10.200.1.6.iscsi-target: P 49:301(252) ack 1 win 129 nop,nop,timestamp 296394145 296394145 00:03:04.584626 IP (tos 0x0, ttl 64, id 51729, offset 0, flags [DF], proto: TCP (6), length: 52) 10.200.1.6.iscsi-target 10.200.1.6.20331: ., cksum 0x4afc (correct), 1:1(0) ack 301 win 133 nop,nop,timestamp 296394145 296394145 00:03:04.584668 IP (tos 0x0, ttl 64, id 51730, offset 0, flags [DF], proto: TCP (6), length: 244) 10.200.1.6.iscsi-target 10.200.1.6.20331: P 1:193(192) ack 301 win 133 nop,nop,timestamp 296394145 296394145 00:03:04.584684 IP (tos 0x0, ttl 64, id 55724, offset 0, flags [DF], proto: TCP (6), length: 52) 10.200.1.6.20331 10.200.1.6.iscsi-target: ., cksum 0x4a3c (correct), 301:301(0) ack 193 win 133 nop,nop,timestamp 296394145 296394145 00:03:04.584706 IP (tos 0x0, ttl 64, id 55725, offset 0, flags [DF], proto: TCP (6), length: 100) 10.200.1.6.20331 10.200.1.6.iscsi-target: P 301:349(48) ack 193 win 133 nop,nop,timestamp 296394145 296394145 00:03:04.584714 IP (tos 0x0, ttl 64, id 55726, offset 0, flags [DF], proto: TCP (6), length: 68) 10.200.1.6.20331 10.200.1.6.iscsi-target: P, cksum 0x17d2 (incorrect (- 0x3b43), 349:365(16) ack 193 win 133 nop,nop,timestamp 296394145 296394145 00:03:04.584719 IP (tos 0x0, ttl 64, id 51731, offset 0, flags [DF], proto: TCP (6), length: 52) 10.200.1.6.iscsi-target 10.200.1.6.20331: ., cksum 0x49fc (correct), 193:193(0) ack 365 win 133 nop,nop,timestamp 296394145 296394145 00:03:04.584908 IP (tos 0x0, ttl 64, id 51732, offset 0, flags [DF], proto: TCP (6), length: 192) 10.200.1.6.iscsi-target 10.200.1.6.20331: P 193:333(140) ack 365 win 133 nop,nop,timestamp 296394145 296394145 00:03:04.586785 IP (tos 0x0, ttl 64, id 55727, offset 0, flags [DF], proto: TCP (6), length: 52) 10.200.1.6.20331 10.200.1.6.iscsi-target: F, cksum 0x4969 (correct), 365:365(0) ack 333 win 137 nop,nop,timestamp 296394147 296394145 00:03:04.586807 IP (tos 0x0, ttl 64, id 51733, offset 0, flags [DF], proto: TCP (6), length: 52) 10.200.1.6.iscsi-target 10.200.1.6.20331: F, cksum 0x496a (correct), 333:333(0) ack 366 win 133 nop,nop,timestamp 296394147 296394147 00:03:04.586816 IP (tos 0x0, ttl 64, id 55728, offset 0, flags [DF], proto: TCP (6), length: 52) 10.200.1.6.20331 10.200.1.6.iscsi-target: ., cksum 0x4966 (correct), 366:366(0) ack 334 win 137 nop,nop,timestamp 296394147 296394147 16 packets captured 32 packets received by filter 0 packets dropped by kernel -- Check the timestamps and you will see either three or six second delays between groups of three packets. [r...@lh6 ~]# iscsiadm -m node -T iqn.2009-10.net.linush:storage.disk1.sys1.asmdg -p 10.200.1.6:3260 -I iface0 -l Logging in to [iface: iface0, target: iqn.2009-10.net.linush:storage.disk1.sys1.asmdg, portal: 10.200.1.6,3260] iscsiadm: Could not login to [iface: iface0, target: iqn.2009-10.net.linush:storage.disk1.sys1.asmdg, portal: 10.200.1.6,3260]: iscsiadm: initiator reported error (8 - connection timed out) [r...@lh6 iscsi]# tcpdump -i lo -n -vv 00:01:07.521652 IP (tos 0x0, ttl 64, id 4451, offset 0, flags [DF], proto: TCP (6),
[CentOS] Possible to run iscsi-target and initiator on same server?
I am trying to install Oracle RAC in a two node cluster for testing purposes, so performance is not something that concerns me. I just want to go through the process all the way to creating a database. I have all the prerequisites except the shared storage and thought I'd give this a try. I'm running: - CentOS 5.3 kernel 2.6.18-164.el5 - iscsitarget-1.4.18-1 - iscsi-initiator-utils-6.2.0.868-0.18.el5_3.1 I can discover and login to the node using iscsiadm on the server that is not also running iet, and see the new scsi disk. When I try to login using iscsiadm on the server that is running the ietd daemon, I see packets going over the lo interface in both directions, but I get error 8 - connection timed out. Wireshark is reporting TCP Previous segment lost errors with large sequence numbers like 2999833 and 8999718. Has anybody tried this, and can anybody offer any help? Thanks. Linus ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Possible to run iscsi-target and initiator on same server?
On Fri, 2009-10-09 at 17:53 -0400, Ross Walker wrote: On Fri, Oct 9, 2009 at 5:37 PM, C Linus Hicks lin...@verizon.net wrote: I am trying to install Oracle RAC in a two node cluster for testing purposes, so performance is not something that concerns me. I just want to go through the process all the way to creating a database. I have all the prerequisites except the shared storage and thought I'd give this a try. I'm running: - CentOS 5.3 kernel 2.6.18-164.el5 - iscsitarget-1.4.18-1 - iscsi-initiator-utils-6.2.0.868-0.18.el5_3.1 I can discover and login to the node using iscsiadm on the server that is not also running iet, and see the new scsi disk. When I try to login using iscsiadm on the server that is running the ietd daemon, I see packets going over the lo interface in both directions, but I get error 8 - connection timed out. Wireshark is reporting TCP Previous segment lost errors with large sequence numbers like 2999833 and 8999718. Has anybody tried this, and can anybody offer any help? You can only do that if you use blockio for your targets, otherwise fileio will cause a deadlock on the page cache between the target's usage of it and the initiator's usage of it. So for iet, that means /etc/iet/ietd.conf should define the Lun like this: Lun 0 Path=/dev/sdb,Type=blockio,ScsiId=asmdg,ScsiSN=dg0 If that's all it takes to make it do blockio instead of fileio, then that is already the case. Deadlocks on the cache pages - wouldn't that only affect I/O and not logging in? Linus ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Possible to run iscsi-target and initiator on same server?
On Fri, 2009-10-09 at 21:42 -0400, Ross Walker wrote: On Oct 9, 2009, at 6:14 PM, C Linus Hicks wrote: So for iet, that means /etc/iet/ietd.conf should define the Lun like this: Lun 0 Path=/dev/sdb,Type=blockio,ScsiId=asmdg,ScsiSN=dg0 If that's all it takes to make it do blockio instead of fileio, then that is already the case. Deadlocks on the cache pages - wouldn't that only affect I/O and not logging in? Ok, well at least that's covered. Is iptables disabled? Also the latest version of IET won't advertise the loopback on discovery unless you are discovering on that same same loopback address. You can still statically connect though, which I recommend for loopback connections. Yep, iptables doesn't run on that machine, the service is disabled. And I'm just using the one IP address on that machine. Here's my /var/lib/iscsi/ifaces/iface0 file: iface.transport_name = tcp iface.hwaddress = 00:1D:92:B4:50:6E Is the transport_name for loopback still tcp? The discovery appears to work properly: [r...@lh6 iscsi]# iscsiadm -m discovery -t st -p 10.200.1.6:3260 -I iface0 -P 1 Target: iqn.2009-10.net.linush:storage.disk1.sys1.asmdg Portal: 10.200.1.6:3260,1 Iface Name: iface0 I found a way to make the entry in /var/lib/iscsi/static which is just a symbolic link back to the entry in /var/lib/iscsi/nodes, but you must be seeing different documentation because I don't see any thing that talks about logging in using the static entry. At any rate, I run this command and get the output as shown: [r...@lh6 iscsi]# iscsiadm -m node -T iqn.2009-10.net.linush:storage.disk1.sys1.asmdg -p 10.200.1.6:3260 -l Logging in to [iface: iface0, target: iqn.2009-10.net.linush:storage.disk1.sys1.asmdg, portal: 10.200.1.6,3260] iscsiadm: Could not login to [iface: iface0, target: iqn.2009-10.net.linush:storage.disk1.sys1.asmdg, portal: 10.200.1.6,3260]: iscsiadm: initiator reported error (8 - connection timed out) And here's the node: [r...@lh6 iscsi]# cat nodes/iqn.2009-10.net.linush\:storage.disk1.sys1.asmdg/10.200.1.6\,3260\,1/iface0 # BEGIN RECORD 2.0-868 node.name = iqn.2009-10.net.linush:storage.disk1.sys1.asmdg node.tpgt = 1 node.startup = manual iface.hwaddress = 00:1D:92:B4:50:6E iface.iscsi_ifacename = iface0 iface.net_ifacename = default iface.transport_name = tcp node.discovery_port = 0 node.discovery_type = static node.session.initial_cmdsn = 0 node.session.initial_login_retry_max = 4 node.session.cmds_max = 128 node.session.queue_depth = 32 node.session.auth.authmethod = None node.session.timeo.replacement_timeout = 120 node.session.err_timeo.abort_timeout = 15 node.session.err_timeo.lu_reset_timeout = 30 node.session.err_timeo.host_reset_timeout = 60 node.session.iscsi.FastAbort = Yes node.session.iscsi.InitialR2T = No node.session.iscsi.ImmediateData = Yes node.session.iscsi.FirstBurstLength = 262144 node.session.iscsi.MaxBurstLength = 16776192 node.session.iscsi.DefaultTime2Retain = 0 node.session.iscsi.DefaultTime2Wait = 2 node.session.iscsi.MaxConnections = 1 node.session.iscsi.MaxOutstandingR2T = 1 node.session.iscsi.ERL = 0 node.conn[0].address = 10.200.1.6 node.conn[0].port = 3260 node.conn[0].startup = manual node.conn[0].tcp.window_size = 524288 node.conn[0].tcp.type_of_service = 0 node.conn[0].timeo.logout_timeout = 15 node.conn[0].timeo.login_timeout = 15 node.conn[0].timeo.auth_timeout = 45 node.conn[0].timeo.noop_out_interval = 5 node.conn[0].timeo.noop_out_timeout = 5 node.conn[0].iscsi.MaxRecvDataSegmentLength = 131072 node.conn[0].iscsi.HeaderDigest = None,CRC32C node.conn[0].iscsi.IFMarker = No node.conn[0].iscsi.OFMarker = No # END RECORD From ifconfig: eth2 Link encap:Ethernet HWaddr 00:1D:92:B4:50:6E inet addr:10.200.1.6 Bcast:10.200.1.255 Mask:255.255.255.0 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SATA tape drive on 4.7
On Mon, 2009-03-23 at 22:22 -0400, C Linus Hicks wrote: On Mon, 2009-03-23 at 00:39 -0400, Ross Walker wrote: This seems it may be a bad memory issue. When star is running it is causing a lot of io to be cached putting pressure on regions of memory that might otherwise go unused. Think about running a memtest first or just swap the memory out for other memory completely compatible with your chipset since memory is probably cheaper then your time is these days. You can always test that memory offline and if it's ok redeploy it otherwise a memtest on a machine with a large memory could take days. -Ross So I ran memtest86 v1.65 for about 12 hours completing five passes on 8GB with no errors. I believe my memory is good. Linus Just FYI, I will be away until 3/31. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SATA tape drive on 4.7
On Mon, 2009-03-23 at 00:39 -0400, Ross Walker wrote: This seems it may be a bad memory issue. When star is running it is causing a lot of io to be cached putting pressure on regions of memory that might otherwise go unused. Think about running a memtest first or just swap the memory out for other memory completely compatible with your chipset since memory is probably cheaper then your time is these days. You can always test that memory offline and if it's ok redeploy it otherwise a memtest on a machine with a large memory could take days. -Ross So I ran memtest86 v1.65 for about 12 hours completing five passes on 8GB with no errors. I believe my memory is good. Linus ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] SATA tape drive on 4.7
I have gotten a hard system lockup several times using star on my system
with a Quantum DLT-V4 SATA tape drive. I am including what got recorded
in /var/log/messages from the most recent event showing stack trace.
Output from uname -a:
Linux lh10 2.6.9-78.0.13.ELsmp #1 SMP Wed Jan 14 15:55:36 EST 2009
x86_64 x86_64 x86_64 GNU/Linux
Mar 22 22:02:59 lh10 kernel: Bad page state at free_hot_cold_page (in process
'star', page 0102382b1ec8)
Mar 22 22:02:59 lh10 kernel: flags:0x010c mapping:0102146a4240
mapcount:2 count:0
Mar 22 22:02:59 lh10 kernel: Backtrace:
Mar 22 22:02:59 lh10 kernel:
Mar 22 22:02:59 lh10 kernel: Call Trace:8015f0cf{bad_page+112}
8015f7b1{free_hot_cold_page+130}
Mar 22 22:02:59 lh10 kernel:
a00d17b8{:st:sgl_unmap_user_pages+67}
a00d17df{:st:release_buffering+27}
Mar 22 22:02:59 lh10 kernel:a00d6196{:st:st_write+2692}
80194b39{inode_update_time+159}
Mar 22 22:02:59 lh10 kernel:8017beaa{vfs_write+207}
8017bf92{sys_write+69}
Mar 22 22:02:59 lh10 kernel:801102f6{system_call+126}
Mar 22 22:02:59 lh10 kernel: Trying to fix it up, but a reboot is needed
Mar 22 22:02:59 lh10 kernel: Bad page state at free_hot_cold_page (in process
'star', page 01023eb70ed8)
Mar 22 22:02:59 lh10 kernel: flags:0x010c mapping:0102146a4240
mapcount:2 count:0
Mar 22 22:02:59 lh10 kernel: Backtrace:
Mar 22 22:02:59 lh10 kernel:
Mar 22 22:02:59 lh10 kernel: Call Trace:8015f0cf{bad_page+112}
8015f7b1{free_hot_cold_page+130}
Mar 22 22:02:59 lh10 kernel:
a00d17b8{:st:sgl_unmap_user_pages+67}
a00d17df{:st:release_buffering+27}
Mar 22 22:02:59 lh10 kernel:a00d6196{:st:st_write+2692}
80194b39{inode_update_time+159}
Mar 22 22:02:59 lh10 kernel:8017beaa{vfs_write+207}
8017bf92{sys_write+69}
Mar 22 22:02:59 lh10 kernel:801102f6{system_call+126}
Mar 22 22:02:59 lh10 kernel: Trying to fix it up, but a reboot is needed
Mar 22 22:02:59 lh10 kernel: Bad page state at free_hot_cold_page (in process
'star', page 01023d3bc220)
Mar 22 22:02:59 lh10 kernel: flags:0x010c mapping:0102146a4240
mapcount:2 count:0
Mar 22 22:02:59 lh10 kernel: Backtrace:
Mar 22 22:02:59 lh10 kernel:
Mar 22 22:02:59 lh10 kernel: Call Trace:8015f0cf{bad_page+112}
8015f7b1{free_hot_cold_page+130}
Mar 22 22:02:59 lh10 kernel:
a00d17b8{:st:sgl_unmap_user_pages+67}
a00d17df{:st:release_buffering+27}
Mar 22 22:02:59 lh10 kernel:a00d6196{:st:st_write+2692}
80194b39{inode_update_time+159}
Mar 22 22:02:59 lh10 kernel:8017beaa{vfs_write+207}
8017bf92{sys_write+69}
Mar 22 22:02:59 lh10 kernel:801102f6{system_call+126}
Mar 22 22:02:59 lh10 kernel: Trying to fix it up, but a reboot is needed
Mar 22 22:02:59 lh10 kernel: Bad page state at free_hot_cold_page (in process
'star', page 010238c68e80)
Mar 22 22:02:59 lh10 kernel: flags:0x010c mapping:0102146a4240
mapcount:2 count:0
Mar 22 22:03:00 lh10 kernel: Backtrace:
Mar 22 22:03:00 lh10 kernel:
Mar 22 22:03:00 lh10 kernel: Call Trace:8015f0cf{bad_page+112}
8015f7b1{free_hot_cold_page+130}
Mar 22 22:03:00 lh10 kernel:
a00d17b8{:st:sgl_unmap_user_pages+67}
a00d17df{:st:release_buffering+27}
Mar 22 22:03:00 lh10 kernel:a00d6196{:st:st_write+2692}
80194b39{inode_update_time+159}
Mar 22 22:03:00 lh10 kernel:8017beaa{vfs_write+207}
8017bf92{sys_write+69}
Mar 22 22:03:00 lh10 kernel:801102f6{system_call+126}
Mar 22 22:03:00 lh10 kernel: Trying to fix it up, but a reboot is needed
Mar 22 22:03:00 lh10 kernel: Bad page state at free_hot_cold_page (in process
'star', page 01023c14d570)
Mar 22 22:03:00 lh10 kernel: flags:0x010c mapping:0102146a4240
mapcount:2 count:0
Mar 22 22:03:00 lh10 kernel: Backtrace:
Mar 22 22:03:00 lh10 kernel:
Mar 22 22:03:00 lh10 kernel: Call Trace:8015f0cf{bad_page+112}
8015f7b1{free_hot_cold_page+130}
Mar 22 22:03:00 lh10 kernel:
a00d17b8{:st:sgl_unmap_user_pages+67}
a00d17df{:st:release_buffering+27}
Mar 22 22:03:00 lh10 kernel:a00d6196{:st:st_write+2692}
80194b39{inode_update_time+159}
Mar 22 22:03:00 lh10 kernel:8017beaa{vfs_write+207}
8017bf92{sys_write+69}
Mar 22 22:03:00 lh10 kernel:801102f6{system_call+126}
Mar 22 22:03:00 lh10 kernel: Trying to fix it up, but a reboot is needed
Mar 22 22:03:00 lh10 kernel: Bad page state at free_hot_cold_page (in process
'X', page 01023c14d570)
Mar 22 22:03:00 lh10 kernel: flags:0x01020008 mapping:0101ec811360
mapcount:0 count:0
Mar 22 22:03:00 lh10 kernel: Backtrace:
Mar 22 22:03:00 lh10 kernel:
Mar 22 22:03:00 lh10 kernel: Call
