AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@lsi.com
RQ:
SSV:mhbs.lsil.com
NSV:
SSH:
R:<Tom.Truong@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/LSI/INBOX	0	85A1D09038E3C1438820EF7A7FAFDD30010B132878@cosmail01.lsi.com
X-Sylpheed-End-Special-Headers: 1
Date: Fri, 9 Apr 2010 13:32:38 -0700
From: Andrew Sharp <andy.sharp@lsi.com>
To: "Truong, Tom" <Tom.Truong@lsi.com>
Subject: Re: Case HD0000001311811: external-ssh has become read only
Message-ID: <20100409133238.0d3d0871@ripper.onstor.net>
In-Reply-To: <85A1D09038E3C1438820EF7A7FAFDD30010B132878@cosmail01.lsi.com>
References: <20100409120652.03fab923@ripper.onstor.net>
	<85A1D09038E3C1438820EF7A7FAFDD30010B132878@cosmail01.lsi.com>
Organization: LSI
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Ah, it's back working now, mucho thanks!

a


On Fri, 9 Apr 2010 13:38:37 -0600 "Truong, Tom" <Tom.Truong@lsi.com>
wrote:

> OK, since you are the only one logged in, I've rebooted it.  It
> should work now.
> 
> root@external-ssh:~# su - andys
> andys@external-ssh:~$ touch foo
> andys@external-ssh:~$ /bin/rm foo
> andys@external-ssh:~$
> 
> Tom
> 
> -----Original Message-----
> From: Andrew Sharp [mailto:andy.sharp@lsi.com] 
> Sent: Friday, April 09, 2010 12:07 PM
> To: Truong, Tom
> Subject: Re: Case HD0000001311811: external-ssh has become read only
> 
> If you have to reboot it, no problem.  It's not terribly useful right
> now.
> 
> On Fri, 9 Apr 2010 12:57:20 -0600 "Truong, Tom" <Tom.Truong@lsi.com>
> wrote:
> 
> > Hi Andy,
> > 
> > 
> > 
> > You are correct.  I noticed weird error in system log file around
> > 10:41 yesterday.
> > 
> > 
> > 
> > Apr  8 10:21:13 external-ssh -- MARK --
> > 
> > Apr  8
> > 10:41:^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^
> 
> Yuck!
> 
> 
> > @^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^
> > 
> > @^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^
> > 
> > @^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
> > 
> > 
> > 
> > I think there is a problem with the root partition and caused it to
> > mount READ only.
> > 
> > 
> > 
> > root@external-ssh:/home/andys# mount
> > 
> > /dev/sda1 on / type ext3 (rw,errors=remount-ro)
> > 
> > 
> > 
> > I'm trying to find the fix without having to reboot it.
> > 
> > 
> > 
> > Tom
> > 
> > 
> > 
> > -----Original Message-----
> > From: Andrew Sharp [mailto:andy.sharp@lsi.com]
> > Sent: Friday, April 09, 2010 11:39 AM
> > To: Truong, Tom
> > Subject: Re: Case HD0000001311811: external-ssh has become read only
> > 
> > 
> > 
> > Hi Tom,
> > 
> > 
> > 
> > It is simply the root filesystem of the VM.  Even though the mount
> > 
> > command (inside the VM) says it's mounted rw, it's not able to write
> > 
> > for some reason.
> > 
> > 
> > 
> > /usr/bin/X11/xauth:  error in locking authority
> > file /home/andys/.Xauthority
> > 
> > andys@external-ssh:~$ touch foo
> > 
> > touch: cannot touch `foo': Read-only file system
> > 
> > andys@external-ssh:~$ mount
> > 
> > /dev/sda1 on / type ext3 (rw,errors=remount-ro)
> > 
> > proc on /proc type proc (rw,noexec,nosuid,nodev)
> > 
> > /sys on /sys type sysfs (rw,noexec,nosuid,nodev)
> > 
> > varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
> > 
> > varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
> > 
> > udev on /dev type tmpfs (rw,mode=0755)
> > 
> > devshm on /dev/shm type tmpfs (rw)
> > 
> > devpts on /dev/pts type devpts (rw,gid=5,mode=620)
> > 
> > andys@external-ssh:~$
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > On Fri, 9 Apr 2010 11:32:55 -0600 "Truong, Tom" <Tom.Truong@lsi.com>
> > 
> > wrote:
> > 
> > 
> > 
> > > Hi Andy,
> > 
> > >
> > 
> > > What is the path of the file system that you are trying to write
> > > to?
> > 
> > >
> > 
> > > Thanks,
> > 
> > > Tom
> > 
> > >
> > 
> > > ________________________________
> > 
> > > From: IT Service Management [mailto:prdrmdy@lsi.com]
> > 
> > > Sent: Thursday, April 08, 2010 11:01 PM
> > 
> > > To: Truong, Tom
> > 
> > > Subject: Case HD0000001311811, Medium request urgency, has been
> > 
> > > assigned to your group to supervise.
> > 
> > >
> > 
> > > Case HD0000001311811 has been assigned to your group UNIX Admin -
> > 
> > > CA . Open the Support Console on server dcssrv40 to view the case.
> > 
> > >
> > 
> > > Case Id:
> > 
> > >
> > 
> > > HD0000001311811<http://helpdesk.lsi.com/detail.cfm?idcaso=HD0000001311811>
> > 
> > >
> > 
> > > Status:
> > 
> > >
> > 
> > > Assigned
> > 
> > >
> > 
> > > Case Type:
> > 
> > >
> > 
> > > Incident
> > 
> > >
> > 
> > > Priority:
> > 
> > >
> > 
> > > Sev3
> > 
> > >
> > 
> > > Urgency:
> > 
> > >
> > 
> > > Medium
> > 
> > >
> > 
> > > Requester Name:
> > 
> > >
> > 
> > > Andy Sharp
> > 
> > >
> > 
> > > Location:
> > 
> > >
> > 
> > > NA - Campbell, CA 254 East Hacienda Ave (USG2)
> > 
> > >
> > 
> > > Category:
> > 
> > >
> > 
> > > System Administration
> > 
> > >
> > 
> > > Type:
> > 
> > >
> > 
> > > UNIX Server
> > 
> > >
> > 
> > > Item:
> > 
> > >
> > 
> > > Issue
> > 
> > >
> > 
> > > Summary:
> > 
> > >
> > 
> > > filesystem of external-ssh read-only
> > 
> > >
> > 
> > > Description:
> > 
> > >
> > 
> > > filesystem of external-ssh read-only
> > 
> > >
> > 
> > > -----Original Message-----
> > 
> > > From: Sharp, Andy
> > 
> > > Sent: Friday, April 09, 2010 11:08 AM
> > 
> > > To: help
> > 
> > > Subject: filesystem of external-ssh read-only
> > 
> > >
> > 
> > > [route to Unix support]
> > 
> > >
> > 
> > > Howdy,
> > 
> > >
> > 
> > > Somehow the filesystem of the system external-ssh has become
> > 
> > > read-only, making it halfway useless. Can someone please fix this?
> > 
> > >
> > 
> > > external-ssh is a VM, in case that helps someone figure out what's
> > 
> > > gone wrong with it.
> > 
> > >
> > 
> > > Thanks,
> > 
> > >
> > 
> > > a
> > 
> > >
> > 
> > >
