Displaying 10 results from an estimated 10 matches for "451c".
Did you mean:
451
2011 Dec 05
2
Booting C 6.0 from C 5.7
...Despite using the usually successful methods of booting into another
operating system from C 5.7, I can't get into C 6.0
Tried:-
title C6-0 (2.6.32-71.el6.x86_64)
rootnoverify (hd0,6)
chainloader +1
and
root (hd0,6)
kernel /boot/vmlinuz-2.6.32-71.el6.x86_64 ro
root=UUID=67c62872-0c69-451c-8412-3c218c0d2cb0 rd_NO_LUKS rd_NO_LVM
rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16
KEYBOARDTYPE=pc KEYTABLE=uk
initrd /boot/initramfs-2.6.32-71.el6.x86_64.img
My default works:-
title CentOS 5.7 #6 (2.6.18-274.7.1.el5)
root (hd0,0)
kernel /boot/vmlinuz-2.6.18-274.7.1.el5 ro r...
2003 May 27
0
(no subject)
...9;t read an inode bitmap while reading inode bitmap
debugfs:
I have also attached the output of tune2fs:
root@0[root]# tune2fs -l /dev/hdb3
tune2fs 1.30-WIP (30-Sep-2002)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: e465598d-e803-451c-866c-6dddca668594
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal filetype sparse_super large_file
Filesystem state: not clean with errors
Errors behavior: Continue
Filesystem OS type: Linux
Inode count:...
2017 Jul 07
0
[Gluster-devel] gfid and volume-id extended attributes lost
We lost the attributes on all the bricks on servers glusterfs2 and glusterfs3 again.
[root at glusterfs2 Log_Files]# gluster volume info
Volume Name: StoragePool
Type: Distributed-Disperse
Volume ID: 149e976f-4e21-451c-bf0f-f5691208531f
Status: Started
Number of Bricks: 20 x (2 + 1) = 60
Transport-type: tcp
Bricks:
Brick1: glusterfs1sds:/ws/disk1/ws_brick
Brick2: glusterfs2sds:/ws/disk1/ws_brick
Brick3: glusterfs3sds:/ws/disk1/ws_brick
Brick4: glusterfs1sds:/ws/disk2/ws_brick
Brick5: glusterfs2sds:/ws/disk2/ws_br...
2017 Jul 08
2
[Gluster-devel] gfid and volume-id extended attributes lost
...com>
wrote:
> We lost the attributes on all the bricks on servers glusterfs2 and
> glusterfs3 again.
>
>
>
> [root at glusterfs2 Log_Files]# gluster volume info
>
>
>
> Volume Name: StoragePool
>
> Type: Distributed-Disperse
>
> Volume ID: 149e976f-4e21-451c-bf0f-f5691208531f
>
> Status: Started
>
> Number of Bricks: 20 x (2 + 1) = 60
>
> Transport-type: tcp
>
> Bricks:
>
> Brick1: glusterfs1sds:/ws/disk1/ws_brick
>
> Brick2: glusterfs2sds:/ws/disk1/ws_brick
>
> Brick3: glusterfs3sds:/ws/disk1/ws_brick
>
>...
2017 Jul 07
3
[Gluster-devel] gfid and volume-id extended attributes lost
On Fri, Jul 7, 2017 at 9:25 PM, Ankireddypalle Reddy <areddy at commvault.com>
wrote:
> 3.7.19
>
These are the only callers for removexattr and only _posix_remove_xattr has
the potential to do removexattr as posix_removexattr already makes sure
that it is not gfid/volume-id. And surprise surprise _posix_remove_xattr
happens only from healing code of afr/ec. And this can only happen
2017 Jul 10
0
[Gluster-devel] gfid and volume-id extended attributes lost
...he bricks on servers glusterfs2 and
>> glusterfs3 again.
>>
>>
>>
>> [root at glusterfs2 Log_Files]# gluster volume info
>>
>>
>>
>> Volume Name: StoragePool
>>
>> Type: Distributed-Disperse
>>
>> Volume ID: 149e976f-4e21-451c-bf0f-f5691208531f
>>
>> Status: Started
>>
>> Number of Bricks: 20 x (2 + 1) = 60
>>
>> Transport-type: tcp
>>
>> Bricks:
>>
>> Brick1: glusterfs1sds:/ws/disk1/ws_brick
>>
>> Brick2: glusterfs2sds:/ws/disk1/ws_brick
>>
&g...
2017 Jul 10
2
[Gluster-devel] gfid and volume-id extended attributes lost
...sterfs3 again.
>>>
>>>
>>>
>>> [root at glusterfs2 Log_Files]# gluster volume info
>>>
>>>
>>>
>>> Volume Name: StoragePool
>>>
>>> Type: Distributed-Disperse
>>>
>>> Volume ID: 149e976f-4e21-451c-bf0f-f5691208531f
>>>
>>> Status: Started
>>>
>>> Number of Bricks: 20 x (2 + 1) = 60
>>>
>>> Transport-type: tcp
>>>
>>> Bricks:
>>>
>>> Brick1: glusterfs1sds:/ws/disk1/ws_brick
>>>
>>> Bric...
2017 Jul 10
0
[Gluster-devel] gfid and volume-id extended attributes lost
...>>>>
>>>> [root at glusterfs2 Log_Files]# gluster volume info
>>>>
>>>>
>>>>
>>>> Volume Name: StoragePool
>>>>
>>>> Type: Distributed-Disperse
>>>>
>>>> Volume ID: 149e976f-4e21-451c-bf0f-f5691208531f
>>>>
>>>> Status: Started
>>>>
>>>> Number of Bricks: 20 x (2 + 1) = 60
>>>>
>>>> Transport-type: tcp
>>>>
>>>> Bricks:
>>>>
>>>> Brick1: glusterfs1sds:/ws/disk1...
2017 Jul 10
2
[Gluster-devel] gfid and volume-id extended attributes lost
...Reddy <areddy at commvault.com<mailto:areddy at commvault.com>> wrote:
We lost the attributes on all the bricks on servers glusterfs2 and glusterfs3 again.
[root at glusterfs2 Log_Files]# gluster volume info
Volume Name: StoragePool
Type: Distributed-Disperse
Volume ID: 149e976f-4e21-451c-bf0f-f5691208531f
Status: Started
Number of Bricks: 20 x (2 + 1) = 60
Transport-type: tcp
Bricks:
Brick1: glusterfs1sds:/ws/disk1/ws_brick
Brick2: glusterfs2sds:/ws/disk1/ws_brick
Brick3: glusterfs3sds:/ws/disk1/ws_brick
Brick4: glusterfs1sds:/ws/disk2/ws_brick
Brick5: glusterfs2sds:/ws/disk2/ws_br...
2017 Jul 13
0
[Gluster-devel] gfid and volume-id extended attributes lost
...gt; wrote:
>
> We lost the attributes on all the bricks on servers glusterfs2 and
> glusterfs3 again.
>
>
>
> [root at glusterfs2 Log_Files]# gluster volume info
>
>
>
> Volume Name: StoragePool
>
> Type: Distributed-Disperse
>
> Volume ID: 149e976f-4e21-451c-bf0f-f5691208531f
>
> Status: Started
>
> Number of Bricks: 20 x (2 + 1) = 60
>
> Transport-type: tcp
>
> Bricks:
>
> Brick1: glusterfs1sds:/ws/disk1/ws_brick
>
> Brick2: glusterfs2sds:/ws/disk1/ws_brick
>
> Brick3: glusterfs3sds:/ws/disk1/ws_brick
>
>...