Re: [CentOS] system shutdown - turning off quotas takes a long time
2010/8/12 Götz Reinicke - IT Koordinator : > Hi, > > recently I had to instal a new raid storage system for our central > fileserver. It is connected by iscsi (1Gbit) and the fielsystems mounted > are 400GB and 1TB and ext3. curretly about 400 GB are used by 1.5 Mio files. > > I turned quota on and did a quota check. > > BUT on reboot the system crashes/hangs during 'turning off quotas' How about turning quota off manually, does it work ok? br, -- Eero, RHCE ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] system shutdown - turning off quotas takes a long time
Am 12.08.10 09:06, schrieb Eero Volotinen: > 2010/8/12 Götz Reinicke - IT Koordinator : >> Hi, >> >> recently I had to instal a new raid storage system for our central >> fileserver. It is connected by iscsi (1Gbit) and the fielsystems mounted >> are 400GB and 1TB and ext3. curretly about 400 GB are used by 1.5 Mio files. >> >> I turned quota on and did a quota check. >> >> BUT on reboot the system crashes/hangs during 'turning off quotas' > > How about turning quota off manually, does it work ok? Hi, I have to addmit, that I did not checked that yet, but was thinking about doing that. The situation is, that this is our production fielserver and our employees would have killed me, if there was more delay ... I try to open an other support timeslot and try this. /Götz -- Götz Reinicke IT-Koordinator Tel. +49 7141 969 420 Fax +49 7141 969 55 420 E-Mail goetz.reini...@filmakademie.de Filmakademie Baden-Württemberg GmbH Akademiehof 10 71638 Ludwigsburg www.filmakademie.de Eintragung Amtsgericht Stuttgart HRB 205016 Vorsitzende des Aufsichtsrats: Prof. Dr. Claudia Hübner Geschäftsführer: Prof. Thomas Schadt smime.p7s Description: S/MIME Cryptographic Signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DHCP problem with virtual interfaces
Il giorno 11/ago/2010, alle ore 20.31, Simone Caldana ha scritto: > > I am collecting port 67 traffic on the dhcp server since this afternoon. I > hope to be able to find out more. further testing revealed that dhclient really asks for the wrong ip (but always sends the client-identifier), and this is due to the poisoned leases file. I am now using /dev/null as leases file for all the virtual dhclients, but I wonder if this disables the entire "keep the old lease" system (which I don't really need) or it simply stays only in memory, which won't really solve the problem. -- Simone Caldana ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] NTFS is more resilient than ext3? Or is it hardware issue?
Hi guys, I don't mean to incite debate or something, just want to share experience and a little curiosity. Back long time ago, we have an old file MS W2K (NTFS) server where due no admin was available to manage it, the server would get power off when the office closed, and auto power on again in the morning. That thing happened for years and it was fine ^^ Recently, I setup a Centos 5.5 file server with ext3 and got power blackout twice and I notice the filesystem got corrupted and also bad sectors. Is it just pure random luck, software or hardware issue? What's your experience? Thank you. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NTFS is more resilient than ext3? Or is it hardware issue?
Hi, ext3 is very reliable, i never had such issues (fsck after a power failure, yes... but no data loss). so i whould say its a hardware issue. Greetings On 08/12/2010 10:55 AM, Fajar Priyanto wrote: > Hi guys, > I don't mean to incite debate or something, just want to share > experience and a little curiosity. > > Back long time ago, we have an old file MS W2K (NTFS) server where due > no admin was available to manage it, the server would get power off > when the office closed, and auto power on again in the morning. That > thing happened for years and it was fine ^^ > > Recently, I setup a Centos 5.5 file server with ext3 and got power > blackout twice and I notice the filesystem got corrupted and also bad > sectors. > > Is it just pure random luck, software or hardware issue? > What's your experience? > > Thank you. > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NTFS is more resilient than ext3? Or is it hardware issue?
2010/8/12 Fajar Priyanto : > Hi guys, > I don't mean to incite debate or something, just want to share > experience and a little curiosity. > > Back long time ago, we have an old file MS W2K (NTFS) server where due > no admin was available to manage it, the server would get power off > when the office closed, and auto power on again in the morning. That > thing happened for years and it was fine ^^ > > Recently, I setup a Centos 5.5 file server with ext3 and got power > blackout twice and I notice the filesystem got corrupted and also bad > sectors. > > Is it just pure random luck, software or hardware issue? > What's your experience? I think it is broken hardware, due to bad sectors. Maybe your harddisk is broken or soon breaking up.. check output from smartctl .. -- Eero, RHCE ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ATI mobility Radeon HD 5470
From: sync > I try to use that version but it does not work ... > Fatal : Module fglrx not found .. Did you check if the module is present somewhere? JD ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NTFS is more resilient than ext3? Or is it hardware issue?
From: Fajar Priyanto > Back long time ago, we have an old file MS W2K (NTFS) server where due > no admin was available to manage it, the server would get power off > when the office closed, and auto power on again in the morning. That > thing happened for years and it was fine ^^ > Recently, I setup a Centos 5.5 file server with ext3 and got power > blackout twice and I notice the filesystem got corrupted and also bad > sectors. > Is it just pure random luck, software or hardware issue? > What's your experience? I am pretty sure bad sectors = corruption. http://en.wikipedia.org/wiki/Bad_sector JD ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Date drift and ntpd
We have a local time server and all of our machines are pointed at it for the time. How can the clock drift by a day and a half? [r...@devserver21 ~]# date Fri Aug 13 14:43:29 EDT 2010 [r...@devserver21 ~]# rdate -s 192.168.1.67 [r...@devserver21 ~]# date Thu Aug 12 07:02:39 EDT 2010 [r...@devserver21 ~]# cat /etc/ntp.conf | grep -v ^# | grep -v ^$ restrict default nomodify notrap noquery restrict 127.0.0.1 server 192.168.1.67 server 192.168.1.66 server 192.168.1.65 server 127.127.1.0 # local clock fudge 127.127.1.0 stratum 10 driftfile /var/lib/ntp/drift broadcastdelay 0.008 keys/etc/ntp/keys -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100- - +1 (443) 269-1555 x333Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Date drift and ntpd
Jason Pyeron sent a missive on 2010-08-12: > We have a local time server and all of our machines are pointed at it > for the time. > > How can the clock drift by a day and a half? > > [r...@devserver21 ~]# date > Fri Aug 13 14:43:29 EDT 2010 > [r...@devserver21 ~]# rdate -s 192.168.1.67 > [r...@devserver21 ~]# date > Thu Aug 12 07:02:39 EDT 2010 > [r...@devserver21 ~]# cat /etc/ntp.conf | grep -v ^# | grep -v ^$ > restrict default nomodify notrap noquery restrict 127.0.0.1 server > 192.168.1.67 server 192.168.1.66 server 192.168.1.65 > server 127.127.1.0 # local clock > fudge 127.127.1.0 stratum 10 > driftfile /var/lib/ntp/drift > broadcastdelay 0.008 > keys/etc/ntp/keys > > Hi, It is unlikely that the machine in question drifted forward in time if ntpd was running. Have a look at the logs /var/log/messages it should contain the ntpd log messages which will help you determine what happened to the time. Also check that ntpd is running with: "service ntpd status" and also "chkconfig ntpd --list" will show the startup position of ntpd HTH Simon. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Date drift and ntpd
> -Original Message- > From: centos-boun...@centos.org > [mailto:centos-boun...@centos.org] On Behalf Of Simon Billis > Sent: Thursday, August 12, 2010 7:36 > To: 'CentOS mailing list' > Subject: Re: [CentOS] Date drift and ntpd > > Jason Pyeron sent a missive on 2010-08-12: > > > We have a local time server and all of our machines are > pointed at it > > for the time. > > > > How can the clock drift by a day and a half? > > > > [r...@devserver21 ~]# date > > Fri Aug 13 14:43:29 EDT 2010 > > [r...@devserver21 ~]# rdate -s 192.168.1.67 > > [r...@devserver21 ~]# date > > Thu Aug 12 07:02:39 EDT 2010 > > [r...@devserver21 ~]# cat /etc/ntp.conf | grep -v ^# | grep -v ^$ > > restrict default nomodify notrap noquery restrict 127.0.0.1 server > > 192.168.1.67 server 192.168.1.66 server 192.168.1.65 > > server 127.127.1.0 # local clock > > fudge 127.127.1.0 stratum 10 > > driftfile /var/lib/ntp/drift > > broadcastdelay 0.008 > > keys/etc/ntp/keys > > > > > > Hi, > > It is unlikely that the machine in question drifted forward > in time if ntpd was running. Have a look at the logs > /var/log/messages it should contain the ntpd log messages [r...@devserver21 ~]# grep ntpd /var/log/messages Jul 28 20:34:41 devserver21 ntpd[3475]: synchronized to 192.168.1.65, stratum 3 Jul 28 21:08:00 devserver21 ntpd[3475]: synchronized to LOCAL(0), stratum 10 Jul 28 21:08:00 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 21:08:11 devserver21 ntpd[3475]: synchronized to 192.168.1.66, stratum 3 Jul 28 21:24:58 devserver21 ntpd[3475]: synchronized to 192.168.1.65, stratum 3 Jul 28 21:41:26 devserver21 ntpd[3475]: synchronized to 192.168.1.67, stratum 3 Jul 28 21:42:16 devserver21 ntpd[3475]: synchronized to LOCAL(0), stratum 10 Jul 28 21:42:16 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 21:42:34 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 21:43:37 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 21:44:41 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 21:45:44 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 21:46:45 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 21:47:50 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 21:48:55 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 21:49:57 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 21:50:59 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 21:52:03 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 21:53:05 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 21:54:06 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 21:55:10 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 21:56:13 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 21:57:16 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 21:58:20 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 21:59:23 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 22:00:28 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 22:01:32 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 22:02:35 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 22:03:38 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 22:04:41 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 22:05:44 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 22:06:49 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 22:07:53 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 22:08:57 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 22:10:00 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 22:11:03 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 22:12:07 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 22:13:13 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 22:14:17 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 22:15:11 devserver21 ntpd[3475]: synchronized to 192.168.1.66, stratum 3 Jul 28 22:31:41 devserver21 ntpd[3475]: synchronized to LOCAL(0), stratum 10 Jul 28 22:31:41 devserver21 ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 22:31:59 devserver21 n
[CentOS] tar - ssh - standard out
Hi I have a process that creates 'some data' and outputs this to standard out and i want to shift this data over ssh to a remote box without ever writing anything locally. I have been experimenting with tar to create the archive as the i dont know what the contents of 'some data' might be so i just need to capture it and output it on the other side. I have been trying with $ tar czf - . | ssh -q 192.168.122.2 "tar xzf -" and this works fine to create an archive of this '.' directory and pipe that over to the other side but i want to take standard out so $ tar czf - `the thing that generates standard out here` | ssh -q 192.168.122.2 "tar xzf -" Would that work or is there a better way to get this over to the other side? It needs to be a data stream though so things like scp and rsync are no good and i need to know what the command is on the remote side being run so that i can restrict this in the ssh public key on the remote side. thanks ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Date drift and ntpd
Hi, > > Jason Pyeron sent a missive on 2010-08-12: > > > > > We have a local time server and all of our machines are > > pointed at it > > > for the time. > > > > > > How can the clock drift by a day and a half? > > > > > > [r...@devserver21 ~]# date > > > Fri Aug 13 14:43:29 EDT 2010 > > > [r...@devserver21 ~]# rdate -s 192.168.1.67 > > > [r...@devserver21 ~]# date > > > Thu Aug 12 07:02:39 EDT 2010 > > > [r...@devserver21 ~]# cat /etc/ntp.conf | grep -v ^# | grep -v ^$ > > > restrict default nomodify notrap noquery restrict 127.0.0.1 server > > > 192.168.1.67 server 192.168.1.66 server 192.168.1.65 > > > server 127.127.1.0 # local clock > > > fudge 127.127.1.0 stratum 10 > > > driftfile /var/lib/ntp/drift > > > broadcastdelay 0.008 > > > keys/etc/ntp/keys > > > > > > > > > > Hi, > > > > It is unlikely that the machine in question drifted forward > > in time if ntpd was running. Have a look at the logs > > /var/log/messages it should contain the ntpd log messages > > [r...@devserver21 ~]# grep ntpd /var/log/messages > /SNIP > Jul 29 17:47:24 devserver21 ntpd[3475]: synchronized to LOCAL(0), > stratum 10 > Aug 12 22:48:29 devserver21 ntpd[3475]: sendto(192.168.1.66): Operation > not > permitted > [r...@devserver21 ~]# uptime > 08:10:19 up 164 days, 9:56, 2 users, load average: 0.20, 0.54, 0.81 > [r...@devserver21 ~]# What happened between July 29 and now? Is there nothing in the logs for that period? Rgds S. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Date drift and ntpd
Hi, > > Jason Pyeron sent a missive on 2010-08-12: > > > > > We have a local time server and all of our machines are > > pointed at it > > > for the time. > > > > > > How can the clock drift by a day and a half? > > /SNIP > > It is unlikely that the machine in question drifted forward > > in time if ntpd was running. Have a look at the logs > > /var/log/messages it should contain the ntpd log messages > > [r...@devserver21 ~]# grep ntpd /var/log/messages > > Jul 28 20:34:41 devserver21 ntpd[3475]: synchronized to 192.168.1.65, > stratum 3 > Jul 28 21:08:00 devserver21 ntpd[3475]: synchronized to LOCAL(0), > stratum 10 > Jul 28 21:08:00 devserver21 ntpd[3475]: frequency error -512 PPM > exceeds > tolerance 500 PPM This indicates the hardware clock frequency error exceeds the rate the kernel can correct. This could be a hardware or a kernel problem. /SNIP > Jul 28 23:06:05 devserver21 ntpd[3475]: time reset +0.554019 s > Jul 28 23:10:14 devserver21 ntpd[3475]: synchronized to LOCAL(0), > stratum 10 > Jul 28 23:17:36 devserver21 ntpd[3475]: synchronized to 192.168.1.67, > stratum 3 > Jul 28 23:20:46 devserver21 ntpd[3475]: synchronized to 192.168.1.66, > stratum 3 > Jul 28 23:22:52 devserver21 ntpd[3475]: synchronized to 192.168.1.65, > stratum 3 > Jul 28 23:33:28 devserver21 ntpd[3475]: synchronized to 192.168.1.65, > stratum 3 > Jul 28 23:34:37 devserver21 ntpd[3475]: time reset -0.866445 s /SNIP > Jul 29 00:42:44 devserver21 ntpd[3475]: time reset -0.922073 s /SNIP > Jul 29 10:50:57 devserver21 ntpd[3475]: time reset -1.638135 s /SNIP > Jul 29 15:59:17 devserver21 ntpd[3475]: time reset -1.599691 s /SNIP The above lines show that the time on the server was gaining slightly - but this could be caused by the stratum 3 server losing time slightly due to loading issues perhaps or by a hardware fault locally > Aug 12 22:48:29 devserver21 ntpd[3475]: sendto(192.168.1.66): Operation > not > permitted I suspect that you have a firewall in place that is blocking the outgoing connections from this point. Rgds S. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Date drift and ntpd
> -Original Message- > From: centos-boun...@centos.org > [mailto:centos-boun...@centos.org] On Behalf Of Simon Billis > Sent: Thursday, August 12, 2010 8:14 > To: 'CentOS mailing list' > Subject: Re: [CentOS] Date drift and ntpd > > Hi, > > > > Jason Pyeron sent a missive on 2010-08-12: > > > > > > > We have a local time server and all of our machines are > > > pointed at it > > > > for the time. > > > > > > > > How can the clock drift by a day and a half? > > > > > > > > [r...@devserver21 ~]# date > > > > Fri Aug 13 14:43:29 EDT 2010 > > > > [r...@devserver21 ~]# rdate -s 192.168.1.67 > > > > [r...@devserver21 ~]# date > > > > Thu Aug 12 07:02:39 EDT 2010 > > > > [r...@devserver21 ~]# cat /etc/ntp.conf | grep -v ^# | > grep -v ^$ > > > > restrict default nomodify notrap noquery restrict > 127.0.0.1 server > > > > 192.168.1.67 server 192.168.1.66 server 192.168.1.65 > > > > server 127.127.1.0 # local clock > > > > fudge 127.127.1.0 stratum 10 > > > > driftfile /var/lib/ntp/drift > > > > broadcastdelay 0.008 > > > > keys/etc/ntp/keys > > > > > > > > > > > > > > Hi, > > > > > > It is unlikely that the machine in question drifted > forward in time > > > if ntpd was running. Have a look at the logs /var/log/messages it > > > should contain the ntpd log messages > > > > [r...@devserver21 ~]# grep ntpd /var/log/messages > /SNIP > > Jul 29 17:47:24 devserver21 ntpd[3475]: synchronized to LOCAL(0), > > stratum 10 Aug 12 22:48:29 devserver21 ntpd[3475]: > > sendto(192.168.1.66): Operation not permitted > > [r...@devserver21 ~]# uptime > > 08:10:19 up 164 days, 9:56, 2 users, load average: 0.20, 0.54, > > 0.81 > > [r...@devserver21 ~]# > > What happened between July 29 and now? Is there nothing in > the logs for that period? > Nothing of note, I do have full logs from those days... [r...@devserver21 ~]# grep ' 00:00:.. devserver21 arpwatch: bogon 192.168.1.67 0:30:67:0:cf:fd' /var/log/messages Jul 26 00:00:37 devserver21 arpwatch: bogon 192.168.1.67 0:30:67:0:cf:fd Jul 27 00:00:47 devserver21 arpwatch: bogon 192.168.1.67 0:30:67:0:cf:fd Jul 28 00:00:44 devserver21 arpwatch: bogon 192.168.1.67 0:30:67:0:cf:fd Jul 29 00:00:41 devserver21 arpwatch: bogon 192.168.1.67 0:30:67:0:cf:fd Jul 30 00:00:08 devserver21 arpwatch: bogon 192.168.1.67 0:30:67:0:cf:fd Jul 31 00:00:08 devserver21 arpwatch: bogon 192.168.1.67 0:30:67:0:cf:fd Aug 1 00:00:14 devserver21 arpwatch: bogon 192.168.1.67 0:30:67:0:cf:fd Aug 2 00:00:22 devserver21 arpwatch: bogon 192.168.1.67 0:30:67:0:cf:fd Aug 3 00:00:11 devserver21 arpwatch: bogon 192.168.1.67 0:30:67:0:cf:fd Aug 4 00:00:58 devserver21 arpwatch: bogon 192.168.1.67 0:30:67:0:cf:fd Aug 5 00:00:06 devserver21 arpwatch: bogon 192.168.1.67 0:30:67:0:cf:fd Aug 6 00:00:06 devserver21 arpwatch: bogon 192.168.1.67 0:30:67:0:cf:fd Aug 7 00:00:03 devserver21 arpwatch: bogon 192.168.1.67 0:30:67:0:cf:fd Aug 8 00:00:43 devserver21 arpwatch: bogon 192.168.1.67 0:30:67:0:cf:fd Aug 9 00:00:16 devserver21 arpwatch: bogon 192.168.1.67 0:30:67:0:cf:fd Aug 10 00:00:08 devserver21 arpwatch: bogon 192.168.1.67 0:30:67:0:cf:fd Aug 11 00:00:34 devserver21 arpwatch: bogon 192.168.1.67 0:30:67:0:cf:fd Aug 12 00:00:19 devserver21 arpwatch: bogon 192.168.1.67 0:30:67:0:cf:fd Aug 13 00:00:20 devserver21 arpwatch: bogon 192.168.1.67 0:30:67:0:cf:fd [r...@devserver21 ~]# -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100- - +1 (443) 269-1555 x333Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] tar - ssh - standard out
Tom Brown wrote: > Hi > > I have a process that creates 'some data' and outputs this to standard > out and i want to shift this data over ssh to a remote box without > ever writing anything locally. I have been experimenting with tar to > create the archive as the i dont know what the contents of 'some data' > might be so i just need to capture it and output it on the other side. > > I have been trying with > > $ tar czf - . | ssh -q 192.168.122.2 "tar xzf -" > > and this works fine to create an archive of this '.' directory and > pipe that over to the other side but i want to take standard out > so > > $ tar czf - `the thing that generates standard out here` | ssh -q > 192.168.122.2 "tar xzf -" > > Would that work or is there a better way to get this over to the other > side? It needs to be a data stream though so things like scp and rsync > are no good and i need to know what the command is on the remote side > being run so that i can restrict this in the ssh public key on the > remote side. > Why do you need any other process involved to work with a data stream? If you want to collect it to a remote file, you can | ssh remotehost 'cat > path_to_file'. Just be sure to quote the redirection so it happens on the remote side. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NTFS is more resilient than ext3? Or is it hardware issue?
On 08/12/2010 01:55 AM, Fajar Priyanto wrote: > Hi guys, > I don't mean to incite debate or something, just want to share > experience and a little curiosity. > > Back long time ago, we have an old file MS W2K (NTFS) server where due > no admin was available to manage it, the server would get power off > when the office closed, and auto power on again in the morning. That > thing happened for years and it was fine ^^ > > Recently, I setup a Centos 5.5 file server with ext3 and got power > blackout twice and I notice the filesystem got corrupted and also bad > sectors. > > Is it just pure random luck, software or hardware issue? > What's your experience? > I would say 'luck'. No common system is normally 100% safe against 'pull the plug' shutdowns. Also, it matters how much disk I/O the system is doing. A system that is idle will tolerate 'pull the plug' better than one actually doing something. Additionally, powering up and powering down is the hardest thing you can do to the *hardware*. Servers should be let run 7/24 - they last longer. Finally, if power failures are taking the machine down, buy a UPS and connect the monitoring cable. I like APC UPSs and apcupsd for monitoring it and automatically shutting the system if needed. You can improve ext3's resistance to corruption quite a bit if you use the 'journal=data,barrier=1' mount options. Barriers is actually one of the few cases where software RAID or LVM hurts you - they don't honor barriers (at least not in CentOS/RHEL - newer kernels have improved this somewhat). If you are using a hardware RAID card with onboard cache - make **SURE** it has battery backup installed, too, or else turn off the cache completely. If you are using LVM/software RAID you will also need to turn off the hard drives *own* write caches as well. And yes - you are going to take some serious performance hits from doing all this. You are trading performance for reliability in the face of power failures. And use ext4 instead of ext3 (ext4 adds journal checksumming) if you can. Here is an article discussing making linux disk I/O safer: http://www.linux-mag.com/id/7773/ -- Benjamin Franz ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Ethernet Quad
Hello, Someone can indicate some Ethernet device Quad 10/100 to use with CentOS 5.x? Thanks, -- Daniel Bruno http://danielbruno.eti.br ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Ethernet Quad
On 08/12/2010 05:56 AM, Daniel Bruno wrote: > Hello, > > Someone can indicate some Ethernet device Quad 10/100 to use with CentOS 5.x? > I don't know about 10/100. For 10/100/1000 I use Intel quad port boards. They work fine. -- Benjamin Franz ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Ethernet Quad
We have several Quads in use, Myricom & Intel. Bot work well, the Myricoms are cheaper. On 08/12/2010 02:56 PM, Daniel Bruno wrote: > Hello, > > Someone can indicate some Ethernet device Quad 10/100 to use with CentOS 5.x? > > > Thanks, ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] tar - ssh - standard out
On 08/12/2010 05:33 AM, Les Mikesell wrote: > Why do you need any other process involved to work with a data stream? If you > want to collect it to a remote file, you can | ssh remotehost 'cat> > path_to_file'. Just be sure to quote the redirection so it happens on the > remote side. > > At a guess it's the compression he is after. Over a slow link it could make a substantial difference. -- Benjamin Franz ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Date drift and ntpd
Jason Pyeron wrote, On 08/12/2010 08:01 AM: > > >> -Original Message- >> From: centos-boun...@centos.org >> [mailto:centos-boun...@centos.org] On Behalf Of Simon Billis >> Sent: Thursday, August 12, 2010 7:36 >> To: 'CentOS mailing list' >> Subject: Re: [CentOS] Date drift and ntpd >> >> Jason Pyeron sent a missive on 2010-08-12: >> >>> We have a local time server and all of our machines are >> pointed at it >>> for the time. >>> >>> How can the clock drift by a day and a half? >>> >>> [r...@devserver21 ~]# date >>> Fri Aug 13 14:43:29 EDT 2010 >>> [r...@devserver21 ~]# rdate -s 192.168.1.67 >>> [r...@devserver21 ~]# date >>> Thu Aug 12 07:02:39 EDT 2010 >>> [r...@devserver21 ~]# cat /etc/ntp.conf | grep -v ^# | grep -v ^$ >>> restrict default nomodify notrap noquery restrict 127.0.0.1 server >>> 192.168.1.67 server 192.168.1.66 server 192.168.1.65 >>> server 127.127.1.0 # local clock >>> fudge 127.127.1.0 stratum 10 >>> driftfile /var/lib/ntp/drift >>> broadcastdelay 0.008 >>> keys/etc/ntp/keys >>> >>> >> Hi, >> >> It is unlikely that the machine in question drifted forward >> in time if ntpd was running. Have a look at the logs >> /var/log/messages it should contain the ntpd log messages > > [r...@devserver21 ~]# grep ntpd /var/log/messages > > Jul 28 20:34:41 devserver21 ntpd[3475]: synchronized to 192.168.1.65, stratum > 3 > Jul 28 21:08:00 devserver21 ntpd[3475]: synchronized to LOCAL(0), stratum 10 > Jul 28 21:08:00 devserver21 ntpd[3475]: frequency error -512 PPM exceeds > tolerance 500 PPM > Jul 28 21:08:11 devserver21 ntpd[3475]: synchronized to 192.168.1.66, stratum > 3 > Jul 28 21:24:58 devserver21 ntpd[3475]: synchronized to 192.168.1.65, stratum > 3 > Jul 28 21:41:26 devserver21 ntpd[3475]: synchronized to 192.168.1.67, stratum > 3 > Jul 28 21:42:16 devserver21 ntpd[3475]: synchronized to LOCAL(0), stratum 10 > Jul 28 21:42:16 devserver21 ntpd[3475]: frequency error -512 PPM exceeds > tolerance 500 PPM > Jul 28 21:42:34 devserver21 ntpd[3475]: frequency error -512 PPM exceeds > tolerance 500 PPM > Jul 28 21:43:37 devserver21 ntpd[3475]: frequency error -512 PPM exceeds > tolerance 500 PPM > tolerance 500 PPM > Jul 28 22:12:07 devserver21 ntpd[3475]: frequency error -512 PPM exceeds > tolerance 500 PPM > Jul 28 22:13:13 devserver21 ntpd[3475]: frequency error -512 PPM exceeds > tolerance 500 PPM > Jul 28 22:14:17 devserver21 ntpd[3475]: frequency error -512 PPM exceeds > tolerance 500 PPM > Jul 28 22:15:11 devserver21 ntpd[3475]: synchronized to 192.168.1.66, stratum > 3 > Jul 28 22:31:41 devserver21 ntpd[3475]: synchronized to LOCAL(0), stratum 10 > Jul 28 22:31:41 devserver21 ntpd[3475]: frequency error -512 PPM exceeds > tolerance 500 PPM > Jul 29 15:14:01 devserver21 ntpd[3475]: synchronized to LOCAL(0), stratum 10 > Jul 29 15:26:05 devserver21 ntpd[3475]: synchronized to 192.168.1.65, stratum > 3 > Jul 29 15:59:17 devserver21 ntpd[3475]: time reset -1.599691 s > Jul 29 16:03:31 devserver21 ntpd[3475]: synchronized to LOCAL(0), stratum 10 > Jul 29 16:05:38 devserver21 ntpd[3475]: synchronized to 192.168.1.67, stratum > 3 > Jul 29 16:08:46 devserver21 ntpd[3475]: synchronized to 192.168.1.66, stratum > 3 > Jul 29 16:11:55 devserver21 ntpd[3475]: synchronized to 192.168.1.65, stratum > 3 > Jul 29 17:23:57 devserver21 ntpd[3475]: synchronized to 192.168.1.67, stratum > 3 > Jul 29 17:24:59 devserver21 ntpd[3475]: synchronized to LOCAL(0), stratum 10 > Jul 29 17:30:46 devserver21 ntpd[3475]: synchronized to 192.168.1.65, stratum > 3 > Jul 29 17:47:24 devserver21 ntpd[3475]: synchronized to LOCAL(0), stratum 10 > Aug 12 22:48:29 devserver21 ntpd[3475]: sendto(192.168.1.66): Operation not > permitted > [r...@devserver21 ~]# uptime > 08:10:19 up 164 days, 9:56, 2 users, load average: 0.20, 0.54, 0.81 > [r...@devserver21 ~]# Assumption: this is not from any kind of virtual machine. Assumption: Your local time server is NOT a GPS with an ovenized crystal or even a cell phone time source, i.e. NOT very stable. Assumption: the time servers that you are following (192.168.1.6[57]) are: a) each following the same timeserver(s), or at least have one in common. b) peering with one another c) following time servers that are reasonably stable. Assumption: the time farm is on real, non busy (an old cisco router serving as the internet connection to 1000+ computers does not qualify as non busy), hardware and is configured to archive maxpoll 10 or higher. one problem that you have is that your timeserver farm (192.168.1.6[57]) is occasionally loosing its servers, i.e. we see "synchronized to LOCAL(0)" occasionally, which should not happen with a well configured time farm for hours to days, not minutes. the second problem is that a machine which is not intended to be a time server is configured with a local clock with a stratum better than 15. suggestion 1: 65 should have local clock at stratum 13, 66 and 67 should have
Re: [CentOS] Ethernet Quad
On Thu, Aug 12, 2010 at 3:01 PM, Jerry Franz wrote: > On 08/12/2010 05:56 AM, Daniel Bruno wrote: >> Hello, >> >> Someone can indicate some Ethernet device Quad 10/100 to use with CentOS 5.x? >> > > I don't know about 10/100. For 10/100/1000 I use Intel quad port boards. > They work fine. > > -- > Benjamin Franz > ___ Sorry to hijack this thread, but it could be relevant. As matter of interest, do these cards offer lower throughput than 4x single 1GB cards? -- Kind Regards Rudi Ahlers SoftDux Website: http://www.SoftDux.com Technical Blog: http://Blog.SoftDux.com Office: 087 805 9573 Cell: 082 554 7532 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NTFS is more resilient than ext3? Or is it hardware issue?
At Thu, 12 Aug 2010 16:55:29 +0800 CentOS mailing list wrote: > > Hi guys, > I don't mean to incite debate or something, just want to share > experience and a little curiosity. > > Back long time ago, we have an old file MS W2K (NTFS) server where due > no admin was available to manage it, the server would get power off > when the office closed, and auto power on again in the morning. That > thing happened for years and it was fine ^^ > > Recently, I setup a Centos 5.5 file server with ext3 and got power > blackout twice and I notice the filesystem got corrupted and also bad > sectors. > > Is it just pure random luck, software or hardware issue? > What's your experience? We (way back when while I was working at UMass) bought two Gateway desktop boxes (identical machines with identical Quantum SCSI disks). One got MS-Windows NT 4 installed on it, the other RedHat Linux. Within a month the RedHat box reported disk errors (nothing totally fatal, just bad sector I/O). We had the disk replaced with a Seagate SCSI disk and the machine was happy for years. Not a peep out of the NT box for like 7 months, then it basically died due to disk failure. We *suspected* that the disk probably was having trouble all along, but NT was totally 'oblivious' to the errors... > > Thank you. > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > > > -- Robert Heller -- Get the Deepwoods Software FireFox Toolbar! Deepwoods Software-- Linux Installation and Administration http://www.deepsoft.com/ -- Web Hosting, with CGI and Database hel...@deepsoft.com -- Contract Programming: C/C++, Tcl/Tk ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] tar - ssh - standard out
At Thu, 12 Aug 2010 13:11:21 +0100 CentOS mailing list wrote: > > Hi > > I have a process that creates 'some data' and outputs this to standard > out and i want to shift this data over ssh to a remote box without > ever writing anything locally. I have been experimenting with tar to > create the archive as the i dont know what the contents of 'some data' > might be so i just need to capture it and output it on the other side. > > I have been trying with > > $ tar czf - . | ssh -q 192.168.122.2 "tar xzf -" > > and this works fine to create an archive of this '.' directory and > pipe that over to the other side but i want to take standard out > so > > $ tar czf - `the thing that generates standard out here` | ssh -q > 192.168.122.2 "tar xzf -" > > Would that work or is there a better way to get this over to the other > side? It needs to be a data stream though so things like scp and rsync > are no good and i need to know what the command is on the remote side > being run so that i can restrict this in the ssh public key on the > remote side. Why not just do `the thing that generates standard out here` | ssh -q 192.168.122.2 dd of=somethin eg find . | ssh -q 192.168.122.2 dd of=find.out You don't need tar for anything. > > thanks > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > > -- Robert Heller -- Get the Deepwoods Software FireFox Toolbar! Deepwoods Software-- Linux Installation and Administration http://www.deepsoft.com/ -- Web Hosting, with CGI and Database hel...@deepsoft.com -- Contract Programming: C/C++, Tcl/Tk ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Ethernet Quad
On 08/12/2010 06:06 AM, Rudi Ahlers wrote: > On Thu, Aug 12, 2010 at 3:01 PM, Jerry Franz wrote: > >> On 08/12/2010 05:56 AM, Daniel Bruno wrote: >> >>> Someone can indicate some Ethernet device Quad 10/100 to use with CentOS 5.x >> I don't know about 10/100. For 10/100/1000 I use Intel quad port boards. >> They work fine. >> > > > Sorry to hijack this thread, but it could be relevant. > As matter of interest, do these cards offer lower throughput than 4x > single 1GB cards? > > Depends mostly on if you are using PCI/PCI-X vs PCI-express. At high bit rates you can saturate the old PCI bus. A single gigabit port can pretty much saturate a 32-bit PCI bus at 33MHz. PCI-express can go a lot faster. -- Benjamin Franz ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] tar - ssh - standard out
At Thu, 12 Aug 2010 06:05:25 -0700 CentOS mailing list wrote: > > On 08/12/2010 05:33 AM, Les Mikesell wrote: > > Why do you need any other process involved to work with a data stream? If > > you > > want to collect it to a remote file, you can | ssh remotehost 'cat> > > path_to_file'. Just be sure to quote the redirection so it happens on the > > remote side. > > > > > > At a guess it's the compression he is after. Over a slow link it could > make a substantial difference. Just add gzip (or bzip2) to the pipeline: program | bzip2 | ssh -q remote-host 'bunzip2 | remote-program' > -- Robert Heller -- Get the Deepwoods Software FireFox Toolbar! Deepwoods Software-- Linux Installation and Administration http://www.deepsoft.com/ -- Web Hosting, with CGI and Database hel...@deepsoft.com -- Contract Programming: C/C++, Tcl/Tk ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Ethernet Quad
> On 08/12/2010 06:06 AM, Rudi Ahlers wrote: >> On Thu, Aug 12, 2010 at 3:01 PM, Jerry Franz wrote: >> >>> On 08/12/2010 05:56 AM, Daniel Bruno wrote: >>> Someone can indicate some Ethernet device Quad 10/100 to use with CentOS 5.x >>> I don't know about 10/100. For 10/100/1000 I use Intel quad port >>> boards. >>> They work fine. >>> >> >> >> Sorry to hijack this thread, but it could be relevant. >> As matter of interest, do these cards offer lower throughput than 4x >> single 1GB cards? If you should use them in a PCI slot yes, not if you use them in a PCI-X or PCI-e slot (although you could saturate a PCI-e x1 with 4 gbit ports I think). >> >> > > Depends mostly on if you are using PCI/PCI-X vs PCI-express. At high bit > rates you can saturate the old PCI bus. A single gigabit port can pretty > much saturate a 32-bit PCI bus at 33MHz. > > PCI-express can go a lot faster. The Intel Quad cards don't fit (and don't then) in a single PCI slot. The Intel Dual Gbit cards do and you can saturate a PCI slot with it quite easy :) Regards, Michel ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Ethernet Quad
>> As matter of interest, do these cards offer lower throughput than 4x >> single 1GB cards? > Depends mostly on if you are using PCI/PCI-X vs PCI-express. At high bit > rates you can saturate the old PCI bus. A single gigabit port can pretty > much saturate a 32-bit PCI bus at 33MHz. > > PCI-express can go a lot faster. > Benjamin Franz And on current multi CPU / multi core plattforms care to have support for MSI-X on the motherboard and by the Ethernet controller (for 10Gbe and virtualization this is even a must to gain maximum performance). Alexander ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] tar - ssh - standard out
Robert Heller wrote, On 08/12/2010 09:18 AM: > At Thu, 12 Aug 2010 06:05:25 -0700 CentOS mailing list > wrote: > >> On 08/12/2010 05:33 AM, Les Mikesell wrote: >>> Why do you need any other process involved to work with a data stream? If >>> you >>> want to collect it to a remote file, you can | ssh remotehost 'cat> >>> path_to_file'. Just be sure to quote the redirection so it happens on the >>> remote side. >>> >>> >> At a guess it's the compression he is after. Over a slow link it could >> make a substantial difference. > > Just add gzip (or bzip2) to the pipeline: > > program | bzip2 | ssh -q remote-host 'bunzip2 | remote-program' > > or even easier (though maybe not as good a compression as bzip would get if dealing with text only) program | ssh -C -q remote-host 'remote-program' -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] tar - ssh - standard out
On Thu, Aug 12, 2010 at 09:18:31AM -0400, Robert Heller wrote: > program | bzip2 | ssh -q remote-host 'bunzip2 | remote-program' If you're gonna put a compression tool in the pipeline then I recommend you ensure ssh's own on-the-wire compression is turned off 'cos otherwise you're potentially wasting CPU cycles. ssh -q -o 'Compression no' remote-host Yes; this may be the default value but it's always a good thing to ensure sane values are used in cases like this :-) -- rgds Stephen ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Date drift and ntpd
> -Original Message- > From: Todd Denniston > Sent: Thursday, August 12, 2010 9:07 > Jason Pyeron wrote, On 08/12/2010 08:01 AM: > >> -Original Message- > >> From: Simon Billis > >> Sent: Thursday, August 12, 2010 7:36 > >> > >> Jason Pyeron sent a missive on 2010-08-12: > >> > >>> We have a local time server and all of our machines are > >> pointed at it > >>> for the time. > >>> > >>> How can the clock drift by a day and a half? > >>> > >>> [r...@devserver21 ~]# date > >>> Fri Aug 13 14:43:29 EDT 2010 > >>> [r...@devserver21 ~]# rdate -s 192.168.1.67 > >>> [r...@devserver21 ~]# date > >>> Thu Aug 12 07:02:39 EDT 2010 > >>> [r...@devserver21 ~]# cat /etc/ntp.conf | grep -v ^# | grep -v ^$ > >>> restrict default nomodify notrap noquery restrict 127.0.0.1 server > >>> 192.168.1.67 server 192.168.1.66 server 192.168.1.65 > >>> server 127.127.1.0 # local clock > >>> fudge 127.127.1.0 stratum 10 > >>> driftfile /var/lib/ntp/drift > >>> broadcastdelay 0.008 > >>> keys/etc/ntp/keys > >>> > >>> > >> Hi, > >> > >> It is unlikely that the machine in question drifted > forward in time > >> if ntpd was running. Have a look at the logs /var/log/messages it > >> should contain the ntpd log messages > > > > [r...@devserver21 ~]# grep ntpd /var/log/messages Jul 28 > > 20:34:41 devserver21 ntpd[3475]: synchronized to > 192.168.1.65, stratum > > 3 Jul 28 21:08:00 devserver21 ntpd[3475]: synchronized to LOCAL(0), > > stratum 10 Jul 28 21:08:00 devserver21 ntpd[3475]: frequency error > > -512 PPM exceeds tolerance 500 PPM Jul 28 21:08:11 devserver21 > > ntpd[3475]: synchronized to 192.168.1.66, stratum 3 Jul 28 21:24:58 > > devserver21 ntpd[3475]: synchronized to 192.168.1.65, > stratum 3 Jul 28 > > 21:41:26 devserver21 ntpd[3475]: synchronized to > 192.168.1.67, stratum > > 3 Jul 28 21:42:16 devserver21 ntpd[3475]: synchronized to LOCAL(0), > > stratum 10 Jul 28 21:42:16 devserver21 ntpd[3475]: frequency error > > -512 PPM exceeds tolerance 500 PPM Jul 28 21:42:34 devserver21 > > ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 > PPM Jul 28 > > 21:43:37 devserver21 ntpd[3475]: frequency error -512 PPM exceeds > > tolerance 500 PPM > > > tolerance 500 PPM > > Jul 28 22:12:07 devserver21 ntpd[3475]: frequency error -512 PPM > > exceeds tolerance 500 PPM Jul 28 22:13:13 devserver21 ntpd[3475]: > > frequency error -512 PPM exceeds tolerance 500 PPM Jul 28 22:14:17 > > devserver21 ntpd[3475]: frequency error -512 PPM exceeds > tolerance 500 > > PPM Jul 28 22:15:11 devserver21 ntpd[3475]: synchronized to > > 192.168.1.66, stratum 3 Jul 28 22:31:41 devserver21 ntpd[3475]: > > synchronized to LOCAL(0), stratum 10 Jul 28 22:31:41 devserver21 > > ntpd[3475]: frequency error -512 PPM exceeds tolerance 500 PPM > > > Jul 29 15:14:01 devserver21 ntpd[3475]: synchronized to LOCAL(0), > > stratum 10 Jul 29 15:26:05 devserver21 ntpd[3475]: synchronized to > > 192.168.1.65, stratum 3 Jul 29 15:59:17 devserver21 > ntpd[3475]: time > > reset -1.599691 s Jul 29 16:03:31 devserver21 ntpd[3475]: > synchronized > > to LOCAL(0), stratum 10 Jul 29 16:05:38 devserver21 ntpd[3475]: > > synchronized to 192.168.1.67, stratum 3 Jul 29 16:08:46 devserver21 > > ntpd[3475]: synchronized to 192.168.1.66, stratum 3 Jul 29 16:11:55 > > devserver21 ntpd[3475]: synchronized to 192.168.1.65, stratum 3 > > > Jul 29 17:23:57 devserver21 ntpd[3475]: synchronized to > 192.168.1.67, > > stratum 3 Jul 29 17:24:59 devserver21 ntpd[3475]: synchronized to > > LOCAL(0), stratum 10 Jul 29 17:30:46 devserver21 ntpd[3475]: > > synchronized to 192.168.1.65, stratum 3 Jul 29 17:47:24 devserver21 > > ntpd[3475]: synchronized to LOCAL(0), stratum 10 Aug 12 22:48:29 > > devserver21 ntpd[3475]: sendto(192.168.1.66): Operation not > permitted > > [r...@devserver21 ~]# uptime > > 08:10:19 up 164 days, 9:56, 2 users, load average: 0.20, 0.54, > > 0.81 > > [r...@devserver21 ~]# > > Assumption: this is not from any kind of virtual machine. Correct. > Assumption: Your local time server is NOT a GPS with an > ovenized crystal or even a cell phone time source, i.e. NOT > very stable. Correct. > Assumption: the time servers that you are following > (192.168.1.6[57]) are: > a) each following the same timeserver(s), or at least > have one in common. 192.168.1.6[567] are one machine. Time on that one is/has been good. Other machines in the enterprise follow it accurately. > b) peering with one another n/a > c) following time servers that are reasonably stable. Appears to be so. > Assumption: the time farm is on real, non busy (an old cisco > router serving as the internet connection to 1000+ computers > does not qualify as non busy), hardware and is configured to > archive maxpoll 10 or higher. Unknown, assuming the latency is neglibile. The important detail here is that all the machines in the lan have the same time. There is no unusual latency there. >
Re: [CentOS] tar - ssh - standard out
> Why not just do > > `the thing that generates standard out here` | ssh -q 192.168.122.2 dd > of=somethin > > > eg > > find . | ssh -q 192.168.122.2 dd of=find.out > > You don't need tar for anything. alas the thing that generates the output creates 5 or 6 seperate streams in sequence that generate 5 or 6 log files but i dont know in advance the names of these logs. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NTFS is more resilient than ext3? Or is it hardware issue?
On Thursday, August 12, 2010 04:55:29 am Fajar Priyanto wrote: > Back long time ago, we have an old file MS W2K (NTFS) server where due > no admin was available to manage it, the server would get power off > when the office closed, and auto power on again in the morning. That > thing happened for years and it was fine ^^ > Recently, I setup a Centos 5.5 file server with ext3 and got power > blackout twice and I notice the filesystem got corrupted and also bad > sectors. Is the Centos 5.5 box the same hardware that ran W2K? If not, then you can't really compare the systems. Having said that, I have seen pull the plug blackouts on busy servers, NTFS and otherwise, lose data and have hard bad sectors. The reason is that if the hard disk is in the process of writing a sector, and its power falls out from under it, especially if the 12 volts falls before the 5 volts, you can get scribbles on the disk. These scribbles, especially with newer drives that pack data tighter than older drives, can overwrite ordinarily protected servo data; when this happens you lose sectors and sometimes whole tracks of data. The right thing is to run a long SMART test (smartctl is the right tool, but read the man page before using it) and see how many sectors the drive ends up remapping. The remapped data is probably lost, but the drive should still be usable if not too many sectors got scribbled. I had a pair of 250GB Maxtor Maxline II drives get scribbled thanks to a power supply that was losing one of its two 12 volt supply rails; 12 volts is in high demand in modern machines. Both drives now fail the SMART long test, even though all sectors except the 150 or so per drive that got scribbled on are ok. The drives have been in use for several years since the scribble incident, and no additional sectors have been remapped. But I did partition them so that the tracks I knew had seek error issues (thanks to the servo data getting overwritten) are between active partitions. The two disks were in a Windows XP mirrored set; a large part of the NTFS filesystem was corrupted due to the particular location on the disks that got scribbled (both disks got marked as faulted as well). When a disk scribbles in this manner you are going to get corruption of some sort; the amount and kind of corruption will depend entirely on what got scribbled. You really need a UPS to prevent this, with the server having communication with the UPS to at least halt all writes when the power falls. Even if the 5 and 12 volt rails fall at the exact same time (impossible to design for, since the fall time will be determined by the RC time constant of the load of the output, and that is variable with system activity) during a disk write you could easily get problems. Some drives are more tolerant of this type of fault than others, but I've seen examples of drives from all the major brands have hard sector errors due to power supply issues; WD, Seagate, Maxtor, Toshiba, Hitachi, you name it. I've seen it with all the major interface types, too, although enterprise class drives are far less likely to have the problem, but even then one of the more damaged drives I've seen was a Seagate Cheetah 72GB U320 SCSI drive, which ended up with over 2000 bad sectors after a particularly nasty set of power undervolts from a failing power supply in a Dell server (the undervoltage was on the 5 volt rail in this particular case; an oscilloscope trace of the 5V line looked like the Mediterranean costline); that drive ended up with sector 0 fried and all remaps taken, thus essentially a dead drive, even though the majority of it tests good. The test takes a very long time, though, thanks to all the seek errors the overwritten servo areas created. So it is a hardware issue more than likely. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] preupgrade
Hello! Just thought I'd present this problem for comment/help/hints: * want to upgrade from Fedora Core 11 to 13 * I have a 64-bit system with Vista as a host o/s, running VMWare, and FC11 as a client o/s * cloned my FC11 as a backup * ran preupgrade, got expected problem with 200MB /boot, but preupgrade said that it could continue downloading (presumably to the larger partition) so I did * preupgrade told me to reboot, so I did * began upgrade process; ran Test. First oddity: Test said it was testing media for FC10 , but test passed. * Problem#1: after test finished, upgrade wanted me to install a disk. There is no such disk -- preupgrade put the upgrade information mostly into /boot, I presume. * had to shutdown the upgrade process * rebooted (I figured I'd try skipping the test this time) * Problem#2: not running upgrade, instead just does a normal boot into FC11 In inspecting /boot, I see a fair amount of upgrade info there. The help for this indicates that I should be using grub to select the upgrade; there is no grub since FC is running as a virtual machine client. At this point I'm considering downloading FC13, writing DVDs, and doing a new virtual client. I was hoping to avoid all that, especially as my FC11 has never recognized the DVD writer drive, so I'll end up having to do it from another machine. Regards, Chip Campbell ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] preupgrade
On 08/12/2010 03:22 PM, Charles Campbell wrote: > * want to upgrade from Fedora Core 11 to 13 you have the wrong list. try the Fedora lists! - KB ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] xen vs kvm for virtualization on centos/rhel?
as i'm reviewing the courseware for the rhel (centos) course i'm teaching next week, i'm going to ask the occasional question, possibly technical, possibly more policy. first one involves the choice for virtualization. the course has a short section involving virt using xen but everything i've read suggests that red hat is concentrating on kvm for virt. thoughts on that? i have the freedom to replace the xen section with one covering kvm instead. the one thing that hasn't been addressed yet by kvm scripts is that a shutdown/reboot of the host won't do a save/restore of the guests like xen can do. for that reason i still use xen for production systems and only use kvm for testing random distros.___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] xen vs kvm for virtualization on centos/rhel?
On 08/12/2010 05:37 PM, Joe Pruett wrote: [snip] > the one thing that hasn't been addressed yet by kvm scripts is that a > shutdown/reboot of the host won't do a save/restore of the guests like > xen can do. for that reason i still use xen for production systems and > only use kvm for testing random distros. Fedora 13 does save the guest on shutdown so I would expect this will be supported in RHEL6/CentOS 6 too. But when do you actually power down a RHEL/CentOS server? And if you did, wouldn't you have migrated the guests to another box already? Regards, Patrick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS 4 Kernel Update
When this kernel update be released for CentOS 4? http://rhn.redhat.com/errata/RHSA-2010-0606.html Thank you. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] preupgrade
On Thu, 12 Aug 2010, Karanbir Singh wrote: > To: CentOS mailing list > From: Karanbir Singh > Subject: Re: [CentOS] preupgrade > > On 08/12/2010 03:22 PM, Charles Campbell wrote: >> * want to upgrade from Fedora Core 11 to 13 > > you have the wrong list. try the Fedora lists! Hi Chip. There's a lot of help available on the fedora forums: http://forums.fedoraforum.org/ Kind Regards, Keith Roberts - Websites: http://www.php-debuggers.net http://www.karsites.net http://www.raised-from-the-dead.org.uk All email addresses are challenge-response protected with TMDA [http://tmda.net] - ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] problems with yum_priorities on CentOS5/RHEL5
On Wed, 11 Aug 2010, Nick wrote: > To: centos@centos.org > From: Nick > Subject: Re: [CentOS] problems with yum_priorities on CentOS5/RHEL5 > > On 10/08/10 17:52, Keith Roberts wrote: >>> 1. yum check-updates and yum update do *not* warn you of an impending >>>unresolved dependency caused by YP hiding the required package. >>> >>> It seems the only way to find out is if you go ahead and try and perform the >>> update, which potentially leaves you with one or more broken packages. >>> This seems a serious flaw that should be fixed. >> >> Not necessarily so. >> I use '[root]# yum -y --skip-broken update' and this only >> updates the packages that have no depsolving problems. Any >> packages with problems are left out of the update. > > Ok, but this isn't a solution, if the broken dependency is related to > something > you care about. It just the easiest possible resolution to implement. > >>> 2. Not only do higher priority packages totally eclipse lower priorities, >>>whatever version, but yum_priorities also makes it seem like they aren't >>>even present. >> >> Well you can enable all your repos with: >> >> [root]# yum --enablerepo=* --disablerepo=Cmedia5 update (or >> whatever the DVD media repo name is). >> >> I have Centos 5.5, ATrpms, EPEL and remi repos all working >> reasonably well using yum-priorities plugin. > > I do wonder why the problem I've had isn't seen more often, as > perl-Module-Install (the package which requires the eclipsed package, > perl-Archive-Tar) is quite a common dependency of Perl packages. > > However, whether this problem manifests itself would depend on what packages > are > installed, not just which repositories are enabled. Maybe you're just lucky > (or > I'm unlucky), and don't need perl-Module-Install. > > Cheers, > > N I don't seem to be using that package: Available Packages Name : perl-Module-Install Arch : noarch Version: 0.92 Release: 1.el5.rf Size : 156 k Repo : rpmforge Summary: Standalone, extensible Perl module installer URL: http://search.cpan.org/dist/Module-Install/ License: Artistic/GPL Description: Module::Install is a standalone, extensible installer for Perl : modules. It is designed to be a drop-in replacement for : ExtUtils::MakeMaker, and is a descendent of CPAN::MakeMaker. Kind Regards, Keith Roberts - Websites: http://www.php-debuggers.net http://www.karsites.net http://www.raised-from-the-dead.org.uk All email addresses are challenge-response protected with TMDA [http://tmda.net] - ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 4 Kernel Update
On 08/12/2010 05:01 PM, Ramon Nieto wrote: > When this kernel update be released for CentOS 4? > > http://rhn.redhat.com/errata/RHSA-2010-0606.html > I'm working on trying to get it out asap. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Is oprofile still working?
Hi all, Is anyone using oprofile? I'm getting segfaults from opreport at the moment, and I'm not sure if it is opreport, or just me. In case it is something just plain daft I am doing, here is how it goes: opcontrol --reset opcontrol --setup --no-vmlinux opcontrol --start ... now I run my program, /tmp/myprog ... opcontrol --dump opcontrol --shutdown then I run, opreport -l /tmp/myprog and get: warning: [vdso] (tgid:4780 range:0x8d7000-0x8d8000) could not be found. warning: [vdso] (tgid:4784 range:0x86-0x861000) could not be found. CPU: Core Solo / Duo, speed 1067 MHz (estimated) Counted CPU_CLK_UNHALTED events (Unhalted clock cycles) with a unit mask of 0x00 (Unhalted core cycles) count 10 Segmentation fault The problem seems to come when I ask for symbols (-l). I can't seem to get much information out of other running programs either. I'm running the opcontrol commands as root, and I've tried opreport as root or myself. I'm sure I have done this successfully in the past (but this is the first time I have tried it in a while). I have what should be a fully patched CentOS 5.5 here. I see this: https://bugzilla.redhat.com/show_bug.cgi?id=529028 , but it looks to be too old to be relevant (I notice I have the updated binutils that the final link in the bugreport points to). I've tried this on two different machines, but they are similar configurations I guess in that they are both 32bit intel machines. Hywel. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NTFS is more resilient than ext3? Or is it hardware issue?
On Thu, 12 Aug 2010, Benjamin Franz wrote: > To: CentOS mailing list > From: Benjamin Franz > Subject: Re: [CentOS] NTFS is more resilient than ext3? Or is it hardware > issue? > > On 08/12/2010 01:55 AM, Fajar Priyanto wrote: >> Hi guys, >> I don't mean to incite debate or something, just want to share >> experience and a little curiosity. >> >> Back long time ago, we have an old file MS W2K (NTFS) server where due >> no admin was available to manage it, the server would get power off >> when the office closed, and auto power on again in the morning. That >> thing happened for years and it was fine ^^ >> >> Recently, I setup a Centos 5.5 file server with ext3 and got power >> blackout twice and I notice the filesystem got corrupted and also bad >> sectors. >> >> Is it just pure random luck, software or hardware issue? >> What's your experience? >> > > I would say 'luck'. No common system is normally 100% safe against 'pull > the plug' shutdowns. Also, it matters how much disk I/O the system is > doing. A system that is idle will tolerate 'pull the plug' better than > one actually doing something. Additionally, powering up and powering > down is the hardest thing you can do to the *hardware*. Servers should > be let run 7/24 - they last longer. Finally, if power failures are > taking the machine down, buy a UPS and connect the monitoring cable. I > like APC UPSs and apcupsd for monitoring it and automatically shutting > the system if needed. I'm using an APC Back-UPS 650 on my home-built server. It does the job well. When there's a dip in the mains voltage the UPS switches in and keeps things running. I have configured apcupsd to gracefully shut the machine down after a 5 second power outage. That APC UPS has been running for about 6 years now, still no problems with it. I get postcards from APC occasionally, asking if I'd like to trade in my UPS for a newer one. Not now thankyou ;) Kind Regards, Keith Roberts - Websites: http://www.php-debuggers.net http://www.karsites.net http://www.raised-from-the-dead.org.uk All email addresses are challenge-response protected with TMDA [http://tmda.net] - ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ATI mobility Radeon HD 5470
On Thu, 12 Aug 2010 02:28:56 -0700 (PDT) John Doe wrote: > From: sync > > I try to use that version but it does not work ... > > Fatal : Module fglrx not found .. > > Did you check if the module is present somewhere? Hi, I installed ATI in Debian dozens of times. Just tried the same process on SL 5.5 here few minutes before. 1) linux-cat107-install.pdf from ATI download website says what files you have to have installed prior to ATI instalation/kernel compilation https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/linux_cat107-inst.pdf 2) Radeon HD 5 is included in the 10.7 list of ATI drivers 3) Installation went smoothly without a problem 4) ATI driver is named fglrx* 5) search for its mutations ;-) there: lib/modules/fglrx lib-/modules/"kernel-sig"/kernel/drivers/char/drm kernel-sig = your kernel's signature 6) Alas there is not such thing like Debian's modconf to conveniently check/manage installed kernel modules; there is no such file like Debian's /etc/modules with a list of additionally installed kernel modules. (Perhaps someone hints us how to peep into SL kernel modules?) 7) ATI installs aticccle manager + fgl_glxgears (with 3D rotating cube) 8) You __have to change__ "manually" monitor's VertRefresh and HorizSync data in /etc/X11/xorg.conf file, e.g.: Section "Monitor" Identifier "aticonfig-Monitor[0]-0" HorizSync30.0 - 70.0 VertRefresh 50.0 - 120.0 Option "VendorName" "ATI Proprietary Driver" Option "ModelName" "Generic Autodetecting Monitor" Option "DPMS" "true" EndSection and add "Modes" line in Screen section: Section "Screen" Identifier "aticonfig-Screen[0]-0" Device "aticonfig-Device[0]-0" Monitor"aticonfig-Monitor[0]-0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes"1024x768" "800x600" "640x480" EndSubSection EndSection 9) WARNING :-( ATI worked good but I had impression that Xorg's latest radeon driver (found in SL 5.5) worked better, especially during MC window resizing - radeon was making less flickering than ATI proprietary driver. The warning relates to system fonts- ATI changed my system fonts to "something ugly" and in 6 pt size! I use IceWM, but every apps got the same fonts and nothing could be done via IceWM settings, of course. Thank God, I had a magnifying glass at hand... So said I changed X11 settings to previous ones, namely to SL radeon driver. BTW. How to change system font in SL? I tried to find out thru google search but to no avail. And there is no such script like system-config-fonts, why? I hope I were able to help. Regards -- Przemysław Pawełczyk (P2O2) [pron. Pshemislav Paveltchick] http://pp.blast.pl, pp...@o2.pl pgpXtx4XIWXHc.pgp Description: PGP signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] tar - ssh - standard out
On 8/12/2010 8:46 AM, Tom Brown wrote: >> Why not just do >> >> `the thing that generates standard out here` | ssh -q 192.168.122.2 dd >> of=somethin >> >> >> eg >> >> find . | ssh -q 192.168.122.2 dd of=find.out >> >> You don't need tar for anything. > > > alas the thing that generates the output creates 5 or 6 seperate > streams in sequence that generate 5 or 6 log files but i dont know in > advance the names of these logs. You'll have to explain how the streams get sorted out locally before anyone can help you do it remotely. Maybe the program itself could piped each stream through a separate ssh instance. Or if you can wait for output to complete, collect all the files in an otherwise empty directory and rsync the whole thing to the remote. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Ethernet Quad
>>> Sorry to hijack this thread, but it could be relevant. >>> As matter of interest, do these cards offer lower throughput than 4x >>> single 1GB cards? > If you should use them in a PCI slot yes, not if you use them in a PCI-X > or PCI-e slot (although you could saturate a PCI-e x1 with 4 gbit ports I > think). Not with the Intel Pro 1000's. The PCIe versions require a x4 slot in the dual or quad configuration. Can't speak to the PCI-X version as I don't have any in my inventory. -- Drew "Nothing in life is to be feared. It is only to be understood." --Marie Curie ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Ethernet Quad
On 08/12/10 10:35 AM, Drew wrote: > Not with the Intel Pro 1000's. The PCIe versions require a x4 slot in > the dual or quad configuration. Can't speak to the PCI-X version as I > don't have any in my inventory. yeah, a single PCI-E 'lane' (eg, x1) is only about twice as fast as a PCI 32 bit 33Mhz desktop slot. (250MB/sec vs 133MB/sec burst). As soon as you get into multiple devices contending for a channel, actual performance goes down considerably due to the overhead of contention negotiation. PCI-E x4 has 4 of these lanes, so each of the 4 NICs can effectively have a lane to itself. Full duplex gigE is, in theory, capable of 120MB/sec read *and* 120MB/sec write at the same time, so this exceeds that single 32bit/33Mhz PCI slot by quite a lot.. PCI-E x4 is roughly equivalent to PCI-X (100-133Mhz, 64bit, about 1Gbyte/sec), and any high performance IO device in a server should be in a x4 slot. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] xen vs kvm for virtualization on centos/rhel?
> Fedora 13 does save the guest on shutdown so I would expect this will be > supported in RHEL6/CentOS 6 too. But when do you actually power down a > RHEL/CentOS server? And if you did, wouldn't you have migrated the > guests to another box already? > mainly it is an issue for a quick reboot of the host for a kernel update. i guess migration is an option for that as well, but not everyone has that much hardware. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] tar - ssh - standard out
At Thu, 12 Aug 2010 14:46:49 +0100 CentOS mailing list
wrote:
>
> > Why not just do
> >
> > `the thing that generates standard out here` | ssh -q 192.168.122.2 dd
> > of=somethin
> >
> >
> > eg
> >
> > find . | ssh -q 192.168.122.2 dd of=find.out
> >
> > You don't need tar for anything.
>
>
> alas the thing that generates the output creates 5 or 6 seperate
> streams in sequence that generate 5 or 6 log files but i dont know in
> advance the names of these logs.
So the thing (program) does not write to stdout itself? It it does '5
or 6' fopen(".log","w")s? Well, then you need to do:
(mkdir temp && cd temp && thing && tar czvf - . | \
ssh -q 192.168.122.2 tar xvf -) && rm -rf temp
And yes, the log files will be written to the local disk before being
transfered. There is not really anyway around this, unless you were
will / able to rewrite 'thing' to work differently.
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
>
--
Robert Heller -- 978-544-6933
Deepwoods Software-- Download the Model Railroad System
http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows
hel...@deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] tar - ssh - standard out
Rsync works fine for this, keeping group and user
Regards
2010/8/12, Robert Heller :
> At Thu, 12 Aug 2010 14:46:49 +0100 CentOS mailing list
> wrote:
>
>>
>> > Why not just do
>> >
>> > `the thing that generates standard out here` | ssh -q 192.168.122.2 dd
>> > of=somethin
>> >
>> >
>> > eg
>> >
>> > find . | ssh -q 192.168.122.2 dd of=find.out
>> >
>> > You don't need tar for anything.
>>
>>
>> alas the thing that generates the output creates 5 or 6 seperate
>> streams in sequence that generate 5 or 6 log files but i dont know in
>> advance the names of these logs.
>
> So the thing (program) does not write to stdout itself? It it does '5
> or 6' fopen(".log","w")s? Well, then you need to do:
>
> (mkdir temp && cd temp && thing && tar czvf - . | \
> ssh -q 192.168.122.2 tar xvf -) && rm -rf temp
>
> And yes, the log files will be written to the local disk before being
> transfered. There is not really anyway around this, unless you were
> will / able to rewrite 'thing' to work differently.
>
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> http://lists.centos.org/mailman/listinfo/centos
>>
>>
>
> --
> Robert Heller -- 978-544-6933
> Deepwoods Software-- Download the Model Railroad System
> http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows
> hel...@deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
--
Enviado desde mi dispositivo móvil
Jesús Hinojosa Palma
DVinci S.A.C
www: http://www.dvinci.pe
mail: jhinoj...@dvinci.pe
Mobil: +51 1 989097034
Phone: +51 1 7207265
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
[CentOS] Ext3 undelete
I was fooled by a hard link trying to clean up disk space. How can I undelete many files? (time is of the essence as I cannot unmount the partition) -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100- - +1 (443) 269-1555 x333Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Ext3 undelete
Google is you friend.. http://www.xs4all.nl/~carlo17/howto/undelete_ext3.html Good luck! -- Don Krause Head Systems Geek, Waver of Deceased Chickens. Optivus Proton Therapy, Inc. P.O. Box 608 Loma Linda, California 92354 909.799.8327 Tel 909.799.8366 Fax dkra...@optivus.com www.optivus.com "This message represents the official view of the voices in my head." ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Ext3 undelete
> -Original Message- > From: Jason Pyeron > Sent: Thursday, August 12, 2010 17:22 > To: 'CentOS mailing list' > Subject: [CentOS] Ext3 undelete > > I was fooled by a hard link trying to clean up disk space. > > How can I undelete many files? (time is of the essence as I I guess I can release the lvm snapshot... > cannot unmount the > partition) > This directory was too big to backup, http://batleth.sapienti-sat.org/projects/FAQs/ext3-faq.html says I am SOL if I don't know the contents to grep for it... Oh well. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100- - +1 (443) 269-1555 x333Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Ext3 undelete
On Thu, Aug 12, 2010 at 02:26:00PM -0700, Don Krause wrote: > http://www.xs4all.nl/~carlo17/howto/undelete_ext3.html That's an excellent little program. It can take some mucking about to find the invocation that will save a particular file or set of files, but it often can get the job done. It's well supported on its mailing list too. Whit ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Date drift and ntpd
On 8/12/2010 5:07 AM, Jason Pyeron wrote: > > [r...@devserver21 ~]# cat /etc/ntp.conf | grep -v ^# | grep -v ^$ > restrict default nomodify notrap noquery > restrict 127.0.0.1 > server 192.168.1.67 > server 192.168.1.66 > server 192.168.1.65 Some HOWTOs tell you that more time servers is better, on a standard knee-jerk redundancy theory, but they're ignoring two things. First, you already have a fallback: the system's built-in clock. It's perfectly fine to run on that while you ride out your time server's downtime. Second, ntpd, internally, is built on a phase-locked loop, which is supposed to stabilize its time corrections in the face of jitter and other bad things out in the real world. Like anything based on a negative feedback loop, however, it can be destablized with certain inputs. Giving ntpd two or more servers is a pretty good way to destabilize its PLL in the real, non-ideal world we find on the modern Internet. To anyone considering flaming me, please read this first: http://queue.acm.org/detail.cfm?id=1773943 At minimum, read the section "One server is enough". The bit on PLLs about halfway down is also directly relevant. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Ext3 undelete
> -Original Message- > From: centos-boun...@centos.org > [mailto:centos-boun...@centos.org] On Behalf Of Whit Blauvelt > Sent: Thursday, August 12, 2010 17:31 > To: CentOS mailing list > Subject: Re: [CentOS] Ext3 undelete > > On Thu, Aug 12, 2010 at 02:26:00PM -0700, Don Krause wrote: > > > http://www.xs4all.nl/~carlo17/howto/undelete_ext3.html > > That's an excellent little program. It can take some mucking > about to find the invocation that will save a particular file > or set of files, but it often can get the job done. It's well > supported on its mailing list too. > Now the question is will it complete before more than the 100M snapshot is used up... [r...@host67 tmp]# ext3grep $IMAGE --restore-all --after=1281653802 --before=1281656202 Running ext3grep version 0.10.2 Only show/process deleted entries if they are deleted on or after Thu Aug 12 18:56:42 2010 and before Thu Aug 12 19:36:42 2010. WARNING: I don't know what EXT3_FEATURE_COMPAT_EXT_ATTR is. WARNING: EXT3_FEATURE_INCOMPAT_RECOVER is set. This either means that your partition is still mounted, and/or the file system is in an unclean state. Number of groups: 1846 Minimum / maximum journal block: 1545 / 9747 Loading journal descriptors... sorting... done The oldest inode block that is still in the journal, appears to be from 1281635206 = Thu Aug 12 13:46:46 2010 Journal transaction 16090037 wraps around, some data blocks might have been lost of this transaction. Number of descriptors in journal: 7101; min / max sequence numbers: 16089433 / 16090473 Writing output to directory RESTORED_FILES/ Finding all blocks that might be directories. D: block containing directory start, d: block containing more directory entries. Each plus represents a directory start that references the same inode as a directory start that we found previously. Searching group 0: +DD+++D+++DD+++DDD++DDD+DddDDDddDdD+Dddd ddd Thanks everyone... -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100- - +1 (443) 269-1555 x333Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Date drift and ntpd
> -Original Message- > From: centos-boun...@centos.org > [mailto:centos-boun...@centos.org] On Behalf Of Warren Young > Sent: Thursday, August 12, 2010 17:41 > To: CentOS mailing list > Subject: Re: [CentOS] Date drift and ntpd > > On 8/12/2010 5:07 AM, Jason Pyeron wrote: > > > > [r...@devserver21 ~]# cat /etc/ntp.conf | grep -v ^# | grep -v ^$ > > restrict default nomodify notrap noquery restrict 127.0.0.1 server > > 192.168.1.67 server 192.168.1.66 server 192.168.1.65 > > Some HOWTOs tell you that more time servers is better, on a > standard knee-jerk redundancy theory, but they're ignoring two things. > > First, you already have a fallback: the system's built-in > clock. It's perfectly fine to run on that while you ride out > your time server's downtime. > > Second, ntpd, internally, is built on a phase-locked loop, > which is supposed to stabilize its time corrections in the > face of jitter and other bad things out in the real world. > Like anything based on a negative feedback loop, however, it > can be destablized with certain inputs. Giving ntpd two or > more servers is a pretty good way to destabilize its PLL in > the real, non-ideal world we find on the modern Internet. > > To anyone considering flaming me, please read this first: > > http://queue.acm.org/detail.cfm?id=1773943 > > At minimum, read the section "One server is enough". The bit > on PLLs about halfway down is also directly relevant. Okay, I only have one timeserver, but the ntp clients cowardly refuse to use less than 3. Back to the man page... -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100- - +1 (443) 269-1555 x333Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Date drift and ntpd
On 8/12/2010 3:43 PM, Jason Pyeron wrote: > > Okay, I only have one timeserver, I meant that your on-site time server should be relying on only one other outside time server, one stratum up. > but the ntp clients cowardly refuse to use > less than 3. Only one server on a given LAN should be running ntpd. It's overkill for every machine to keep themselves synced with such a complex and fussy server. All the others should just call ntpdate or msntp every hour or so as a cron job to keep their own time close to that of the LAN time server's. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Problem resizing partition of nfs volume
Hi: I have an NFS volume that I'm trying to resize a partition on. Something about the fdisk process is corrupting something on the drive Before running fdisk, I can mount the volume find: $ mount /dev/sdo1 /home ... and the volume is mounted fine. And, $ e2fsck -f /dev/sdo1 /dev/sdo1: clean, ... But then I run fdisk to rewrite the partition table of this drive, to expand the /dev/sdo1 partition w/o losing data: $ fdisk /dev/sdo # Type 'd' to delete the primary partition # Type 'n' for new partition # Type 'p' for primary # Type '1' for 1st # Type Enter for 1st cylinder # Type Enter for last cylinder (full disk) # Type 'w' to finish Calling ioctl() ... Syncing disks ... But then something has gone wrong. $ e2fsck -f /dev/sdo1 e2fsck 1.39 (29-May-2006) Couldn't find ext2 superblock, trying backup blocks... e2fsck: Bad magic number in super-block while trying to open /dev/sdm1 ... And I can't mount the volume any more: $ mount /dev/sdo1 /home mount: you must specify the filesystem type What am I doing wrong? Am I missing a step of the process? Thanks! Dan ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Date drift and ntpd
On 08/12/10 2:51 PM, Warren Young wrote: > > Only one server on a given LAN should be running ntpd. It's overkill > for every machine to keep themselves synced with such a complex and > fussy server. All the others should just call ntpdate or msntp every > hour or so as a cron job to keep their own time close to that of the LAN > time server's. I disagree. Simply setting a systems time at fixed intervals will result in discontinuities in delta time measurements. if the systems local clock is fast, a given time will occur twice, and a delta between two time readings could be negative.if the clock is slow, a delta between two readings would jump by whatever correction. I do think that having one NTP master server onsite which syncs either to a hardware clock (GPS etc), or to 1 to 3 external NTP servers, then having all the rest of your local servers sync to this one NTP master server is the correct architecture.Once an ntpd synchs and stabilizes to its reference, its very low overhead. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problem resizing partition of nfs volume
On 08/12/10 2:56 PM, Dan Yamins wrote: > Hi: > > I have an NFS volume that I'm trying to resize a partition on. > > Something about the fdisk process is corrupting something on the drive > > Before running fdisk, I can mount the volume find: > > $ mount /dev/sdo1 /home > > ... and the volume is mounted fine. > > And, > $ e2fsck -f /dev/sdo1 > /dev/sdo1: clean, ... > > > But then I run fdisk to rewrite the partition table of this drive, to > expand the /dev/sdo1 partition w/o losing data: > > $ fdisk /dev/sdo > # Type 'd' to delete the primary partition > # Type 'n' for new partition > # Type 'p' for primary > # Type '1' for 1st > # Type Enter for 1st cylinder > # Type Enter for last cylinder (full disk) > # Type 'w' to finish > > Calling ioctl() ... > Syncing disks ... > > But then something has gone wrong. > > $ e2fsck -f /dev/sdo1 > e2fsck 1.39 (29-May-2006) > Couldn't find ext2 superblock, trying backup blocks... > e2fsck: Bad magic number in super-block while trying to open /dev/sdm1 ... > > > And I can't mount the volume any more: > $ mount /dev/sdo1 /home > mount: you must specify the filesystem type > > What am I doing wrong? Am I missing a step of the process? yeah, you deleted your file system, then created a new empty partition. instead, you should have used parted(8) or similar to expand the partition, then used resize2fs(8) to expand the file system on this partition to its new size. me, I'd strongly suggest doing a full backup of the partition first with dump(8) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problem resizing partition of nfs volume
cuak David Véjar Soporte y Redes Ferretería Santiago Soluciones de Abastecimiento Lira 919 Santiago, Chile Fono: (56 2) 731 3824 www.ferreteriasantiago.cl -Mensaje original- De: centos-boun...@centos.org [mailto:centos-boun...@centos.org] En nombre de John R Pierce Enviado el: jueves, 12 de agosto de 2010 18:22 Para: CentOS mailing list Asunto: Re: [CentOS] Problem resizing partition of nfs volume On 08/12/10 2:56 PM, Dan Yamins wrote: > Hi: > > I have an NFS volume that I'm trying to resize a partition on. > > Something about the fdisk process is corrupting something on the drive > > Before running fdisk, I can mount the volume find: > > $ mount /dev/sdo1 /home > > ... and the volume is mounted fine. > > And, > $ e2fsck -f /dev/sdo1 > /dev/sdo1: clean, ... > > > But then I run fdisk to rewrite the partition table of this drive, to > expand the /dev/sdo1 partition w/o losing data: > > $ fdisk /dev/sdo > # Type 'd' to delete the primary partition > # Type 'n' for new partition > # Type 'p' for primary > # Type '1' for 1st > # Type Enter for 1st cylinder > # Type Enter for last cylinder (full disk) > # Type 'w' to finish > > Calling ioctl() ... > Syncing disks ... > > But then something has gone wrong. > > $ e2fsck -f /dev/sdo1 > e2fsck 1.39 (29-May-2006) > Couldn't find ext2 superblock, trying backup blocks... > e2fsck: Bad magic number in super-block while trying to open /dev/sdm1 ... > > > And I can't mount the volume any more: > $ mount /dev/sdo1 /home > mount: you must specify the filesystem type > > What am I doing wrong? Am I missing a step of the process? yeah, you deleted your file system, then created a new empty partition. instead, you should have used parted(8) or similar to expand the partition, then used resize2fs(8) to expand the file system on this partition to its new size. me, I'd strongly suggest doing a full backup of the partition first with dump(8) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problem resizing partition of nfs volume
On Thu, Aug 12, 2010 at 6:21 PM, John R Pierce wrote: > On 08/12/10 2:56 PM, Dan Yamins wrote: > > Hi: > > > > I have an NFS volume that I'm trying to resize a partition on. > > > > Something about the fdisk process is corrupting something on the drive > > > > Before running fdisk, I can mount the volume find: > > > > $ mount /dev/sdo1 /home > > > > ... and the volume is mounted fine. > > > > And, > > $ e2fsck -f /dev/sdo1 > > /dev/sdo1: clean, ... > > > > > > But then I run fdisk to rewrite the partition table of this drive, to > > expand the /dev/sdo1 partition w/o losing data: > > > > $ fdisk /dev/sdo > > # Type 'd' to delete the primary partition > > # Type 'n' for new partition > > # Type 'p' for primary > > # Type '1' for 1st > > # Type Enter for 1st cylinder > > # Type Enter for last cylinder (full disk) > > # Type 'w' to finish > > > > Calling ioctl() ... > > Syncing disks ... > > > > But then something has gone wrong. > > > > $ e2fsck -f /dev/sdo1 > > e2fsck 1.39 (29-May-2006) > > Couldn't find ext2 superblock, trying backup blocks... > > e2fsck: Bad magic number in super-block while trying to open /dev/sdm1 > ... > > > > > > And I can't mount the volume any more: > > $ mount /dev/sdo1 /home > > mount: you must specify the filesystem type > > > > What am I doing wrong? Am I missing a step of the process? > > yeah, you deleted your file system, then created a new empty partition. > Luckily I'm doing this via snapshots of an amazon EBS volume ... so this whole thing was done on throw-away-able backup volume, which can be recreated from the original volume at any time. I've just done this, and I've attached the newly-created volume to /dev/sdo. Now I'm trying to use parted. [r...@domu-12-31-39-0e-b2-61 ~]# parted /dev/sdo Error: Error initialising SCSI device /dev/sdo - Invalid argument I _can_ do it on the volume path itself: [r...@domu-12-31-39-0e-b2-61 ~]# parted /dev/sdo1 Using /dev/sdo1 Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) .. but this seems wrong, since I'm trying to edit the partition table not of the partition /dev/sdo1 but of the drive itself. ... Or perhaps I should this? (If so, could you give more explicit instructions?) Perhaps because this is a network attached drive, something virtual that amazon provides.However, the reason I've written to the centOS list is because the same procedure has worked fine with ubuntu images ... so it didnt' seem like an amazon problem Thanks! Dan ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problem resizing partition of nfs volume
On Thu, Aug 12, 2010 at 6:25 PM, David Véjar wrote: > cuak > ? > > -Mensaje original- > De: centos-boun...@centos.org [mailto:centos-boun...@centos.org] En nombre > de John R Pierce > Enviado el: jueves, 12 de agosto de 2010 18:22 > Para: CentOS mailing list > Asunto: Re: [CentOS] Problem resizing partition of nfs volume > > On 08/12/10 2:56 PM, Dan Yamins wrote: > > Hi: > > > > I have an NFS volume that I'm trying to resize a partition on. > > > > Something about the fdisk process is corrupting something on the drive > > > > Before running fdisk, I can mount the volume find: > > > > $ mount /dev/sdo1 /home > > > > ... and the volume is mounted fine. > > > > And, > > $ e2fsck -f /dev/sdo1 > > /dev/sdo1: clean, ... > > > > > > But then I run fdisk to rewrite the partition table of this drive, to > > expand the /dev/sdo1 partition w/o losing data: > > > > $ fdisk /dev/sdo > > # Type 'd' to delete the primary partition > > # Type 'n' for new partition > > # Type 'p' for primary > > # Type '1' for 1st > > # Type Enter for 1st cylinder > > # Type Enter for last cylinder (full disk) > > # Type 'w' to finish > > > > Calling ioctl() ... > > Syncing disks ... > > > > But then something has gone wrong. > > > > $ e2fsck -f /dev/sdo1 > > e2fsck 1.39 (29-May-2006) > > Couldn't find ext2 superblock, trying backup blocks... > > e2fsck: Bad magic number in super-block while trying to open /dev/sdm1 > ... > > > > > > And I can't mount the volume any more: > > $ mount /dev/sdo1 /home > > mount: you must specify the filesystem type > > > > What am I doing wrong? Am I missing a step of the process? > > yeah, you deleted your file system, then created a new empty partition. > > instead, you should have used parted(8) or similar to expand the > partition, then used resize2fs(8) to expand the file system on this > partition to its new size. > > me, I'd strongly suggest doing a full backup of the partition first with > dump(8) > > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Date drift and ntpd
On 8/12/2010 4:15 PM, John R Pierce wrote: >On 08/12/10 2:51 PM, Warren Young wrote: >> >> Only one server on a given LAN should be running ntpd. It's overkill >> for every machine to keep themselves synced with such a complex and >> fussy server. All the others should just call ntpdate or msntp every >> hour or so as a cron job to keep their own time close to that of the LAN >> time server's. > > I disagree. > > Simply setting a systems time at fixed intervals will result in > discontinuities in delta time measurements. if the systems local clock > is fast, a given time will occur twice, and a delta between two time > readings could be negative.if the clock is slow, a delta between two > readings would jump by whatever correction. This is one of the points from the paper I referenced: there are three main uses for clocks, and a single implementation isn't appropriate for all uses. Only an ideal absolute time clock would work for all three cases. Since we don't have that, you have to consider your own case before deciding on a clock synchronization strategy. The strategy I recommended is based on the fact that its worst case behavior (a small negative jump every hour) is not a problem for me. If it is a problem for your application, you need a different design. > Once an ntpd synchs and > stabilizes to its reference, its very low overhead. True only as long as it's being given stable time input. See figure 5 in the paper for the kind of wild, damped oscillations you get with ntpd when the input is not stable. The time series plot is crystal clear, but don't overlook the fact that the IQR plots use different axes. There's a 4x difference hiding behind that bad visual display of quantitative information. (Yes, that's my inner Tufte you're seeing poking out there.) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problem resizing partition of nfs volume
instead, you should have used parted(8) or similar to expand the > partition, then used resize2fs(8) to expand the file system on this > partition to its new size. > > So I'm trying parted on a new, clean volume created from the snapshot, attached to /dev/sdm As I explained before, I can't do $ parted /dev/sdm [r...@domu-12-31-39-0e-b2-61 ~]# parted /dev/sdm Error: Error initialising SCSI device /dev/sdm - Invalid argument I *CAN* do parted on the path: $ parted /dev/sdm1 GNU Parted 1.8.1 Using /dev/sdm1 Welcome to GNU Parted! Type 'help' to view a list of commands. But then i get this error: (parted) resize 1 0 500GB Error: The location 500GB is outside of the device /dev/sdo1. Which is course is true ... (parted) print Disk /dev/sdm1: 21.5GB Sector size (logical/physical): 512B/512B Partition Table: loop Number Start End SizeFile system Flags 1 0.00kB 21.5GB 21.5GB ext3 So I'm not sure where to go from here... thanks! Dan ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Ext3 undelete
> -Original Message- > From: centos-boun...@centos.org > [mailto:centos-boun...@centos.org] On Behalf Of Jason Pyeron > Sent: Thursday, August 12, 2010 17:41 > To: 'CentOS mailing list' > Subject: Re: [CentOS] Ext3 undelete > > > -Original Message- > > From: centos-boun...@centos.org > > [mailto:centos-boun...@centos.org] On Behalf Of Whit Blauvelt > > Sent: Thursday, August 12, 2010 17:31 > > To: CentOS mailing list > > Subject: Re: [CentOS] Ext3 undelete > > > > On Thu, Aug 12, 2010 at 02:26:00PM -0700, Don Krause wrote: > > > > > http://www.xs4all.nl/~carlo17/howto/undelete_ext3.html > > > > That's an excellent little program. It can take some > mucking about to > > find the invocation that will save a particular file or set > of files, > > but it often can get the job done. It's well supported on > its mailing > > list too. > > > > Now the question is will it complete before more than the > 100M snapshot is used up... Searching group 1768: ext3grep: get_block.cc:37: unsigned char* get_block(int, unsigned char*): Assertion `device.good()' failed. Disk filled up... Good by files... > > > [r...@host67 tmp]# ext3grep $IMAGE --restore-all --after=1281653802 > --before=1281656202 > Running ext3grep version 0.10.2 > Only show/process deleted entries if they are deleted on or > after Thu Aug 12 > 18:56:42 2010 and before Thu Aug 12 19:36:42 2010. > > WARNING: I don't know what EXT3_FEATURE_COMPAT_EXT_ATTR is. > WARNING: EXT3_FEATURE_INCOMPAT_RECOVER is set. This either > means that your partition is still mounted, and/or the file > system is in an unclean state. > Number of groups: 1846 > Minimum / maximum journal block: 1545 / 9747 Loading journal > descriptors... sorting... done The oldest inode block that is > still in the journal, appears to be from > 1281635206 = Thu Aug 12 13:46:46 2010 > Journal transaction 16090037 wraps around, some data blocks > might have been lost of this transaction. > Number of descriptors in journal: 7101; min / max sequence > numbers: 16089433 / > 16090473 > Writing output to directory RESTORED_FILES/ Finding all > blocks that might be directories. > D: block containing directory start, d: block containing more > directory entries. > Each plus represents a directory start that references the > same inode as a directory start that we found previously. > > Searching group 0: > +DD+++D+++DD+++DDD++DDD+DddDDDddDdD+Dd > dd > +DD+++D+++DD+++DDD++DDD+DddDDDddDdD+ > ddd > > > Thanks everyone... -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100- - +1 (443) 269-1555 x333Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problem resizing partition of nfs volume
On Thursday 12 August 2010 17:56, Dan Yamins wrote: > I have an NFS volume that I'm trying to resize a partition on. I suggest you try Parted Magic: http://partedmagic.com/ It doesn't do anything you can't do from the command line, but it's much easier to use. -- Yves Bellefeuille "Au Bellefeuille estas malkompetenta juristo au li estas malhonesta; kaj ech tertium datur: ambau malvirtoj en unu homo." -- Heroldo Komunikas, n-ro 447. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Date drift and ntpd
Jason Pyeron wrote: > > >> -Original Message- >> From: centos-boun...@centos.org >> [mailto:centos-boun...@centos.org] On Behalf Of Warren Young >> Sent: Thursday, August 12, 2010 17:41 >> To: CentOS mailing list >> Subject: Re: [CentOS] Date drift and ntpd >> >> On 8/12/2010 5:07 AM, Jason Pyeron wrote: >>> [r...@devserver21 ~]# cat /etc/ntp.conf | grep -v ^# | grep -v ^$ >>> restrict default nomodify notrap noquery restrict 127.0.0.1 server >>> 192.168.1.67 server 192.168.1.66 server 192.168.1.65 >> Some HOWTOs tell you that more time servers is better, on a >> standard knee-jerk redundancy theory, but they're ignoring two things. >> >> First, you already have a fallback: the system's built-in >> clock. It's perfectly fine to run on that while you ride out >> your time server's downtime. >> >> Second, ntpd, internally, is built on a phase-locked loop, >> which is supposed to stabilize its time corrections in the >> face of jitter and other bad things out in the real world. >> Like anything based on a negative feedback loop, however, it >> can be destablized with certain inputs. Giving ntpd two or >> more servers is a pretty good way to destabilize its PLL in >> the real, non-ideal world we find on the modern Internet. >> >> To anyone considering flaming me, please read this first: >> >> http://queue.acm.org/detail.cfm?id=1773943 >> >> At minimum, read the section "One server is enough". The bit >> on PLLs about halfway down is also directly relevant. > > Okay, I only have one timeserver, but the ntp clients cowardly refuse to use > less than 3. Back to the man page... One server should be fine - you must have something else wrong, like your authoritative server not being a low stratum number - or not convinced itself that its time is correct. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problem resizing partition of nfs volume
I was just shown the solution to my problem, using the "sfdisk" program instead of the "fdisk" or "parted" programs.Apparently "parted" could not work because the drive is not really SCSI, and the "fdisk" program is to "incorrect" and was overwriting a portion of the disk. however, "sfdisk" turns out to be more correct -- although more cumbersome to use. Dan On Thu, Aug 12, 2010 at 8:32 PM, Yves Bellefeuille wrote: > On Thursday 12 August 2010 17:56, Dan Yamins wrote: > > > I have an NFS volume that I'm trying to resize a partition on. > > I suggest you try Parted Magic: http://partedmagic.com/ > > It doesn't do anything you can't do from the command line, but it's much > easier to use. > > -- > Yves Bellefeuille > "Au Bellefeuille estas malkompetenta juristo au li estas malhonesta; > kaj ech tertium datur: ambau malvirtoj en unu homo." -- Heroldo > Komunikas, n-ro 447. > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Date drift and ntpd
Warren Young wrote: > > The strategy I recommended is based on the fact that its worst case > behavior (a small negative jump every hour) is not a problem for me. If > it is a problem for your application, you need a different design. It's a bad idea in the general case. If you have scheduled jobs, ntpdate may jump the clock enough to miss the trigger or run them twice, where ntpd always tries to move the clock fractional seconds at a time so as not to let that happen. Plus, ntpdate does no sanity check at all - if the clock source is badly off, the client will follow blindly even if it goes to the wrong century. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] tar - ssh - standard out
On 08/12/2010 06:46 AM, Tom Brown wrote: > alas the thing that generates the output creates 5 or 6 seperate > streams in sequence that generate 5 or 6 log files but i dont know in > advance the names of these logs. If "the thing" is generating log files, then it's not using "standard out". Perhaps you are using that term incorrectly. On a unix-like system, each process has three standard file descriptors when it starts: these are standard output (stdout), standard error (stderr), and standard input (stdin). These three files are inherited from the parent process, which means that your shell normally sets them up for the commands that you run. If you do not redirect any of those three, then they will normally be connected to the controlling terminal (/dev/tty is the controlling terminal for any process). You can use the shell's redirection functions to connect those file descriptors to files rather than to the terminal, or pipe them to another command. If your application is writing its data to a file without your specific redirection, then it's not using stdout and you can not pipe it to another system without writing the data to disk. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
