Displaying 4 results from an estimated 4 matches for "1000205".
Did you mean:
100005
2010 Mar 02
1
lvm problem.
...type, bad option, bad superblock on
/dev/VolGroup00/bah2_home,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
[root@dom0 ~]# dmesg | tail
EXT3-fs: error loading journal.
SCSI device sda: 1953525168 512-byte hdwr sectors (1000205 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 1953525168 512-byte hdwr sectors (1000205 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
EXT3-fs: Unrecognized mount option "...
2013 Mar 28
1
Glusterfs gives up with endpoint not connected
Dear all,
Right out of the blue glusterfs is not working fine any more every now end
the it stops working telling me,
Endpoint not connected and writing core files:
[root at tuepdc /]# file core.15288
core.15288: ELF 64-bit LSB core file AMD x86-64, version 1 (SYSV),
SVR4-style, from 'glusterfs'
My Version:
[root at tuepdc /]# glusterfs --version
glusterfs 3.2.0 built on Apr 22 2011
2010 Jun 22
1
The Host cpu(s) in this machine do not have support for full virtualization
...02A6B0, 03.00C06, max UDMA/133
ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata2.00: configured for UDMA/133
Vendor: ATA Model: WDC WD1002FBYS-0 Rev: 03.0
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 1953525168 512-byte hdwr sectors (1000205 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 1953525168 512-byte hdwr sectors (1000205 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3
sd 0:0:0:0: Attache...
2008 Aug 22
0
[LLVMdev] New llvm-gcc bootstrap failure
2008/7/23 Duncan Sands <baldrick at free.fr>:
> My nightly tester on x86_64-unknown-linux-gnu failed
> to bootstrap llvm-gcc today:
>
> Comparing stages 2 and 3
> Bootstrap comparison failure!
> ./build/read-rtl.o differs
I am having the same problem. It was "introduced" by revision 54811,
so it looks like a memory corruption problem. Investigating.
> The