search for: crititical

Had a drive crash which a very critital inode. e2fshck returns a stream of : Entry '..' in ... (#######) points to inode (2) located in a bad block Pass 3: Checking directory connectivity Root inode is not a directory: aborting e2fsck: aborted /dev/hda4: ***** FILE SYSTEM WAS MODIFIED ***** Floating point exception I'm wondering if I can use debugfs to relocate (rebuild)

Hi Rowland, Thank you for your answer. I think I have found a solution which could solve the issue until the next migration step. It tested it on another server which is not critital : * Joining the server as a member and setup the shares as you suggest * Use nss_ldap instead of nss_winbind (idmap) which will pick my unix ids In this setup it seems I can access to the shares

Rowland, Yes, I mean uidNumber and gidNumber. I'm aware I need to work with AD but at this time I need my unix IDs (on NSS) to keep services working. Not only for files ownership, but also for some other services. Yeah, that's complex... If I undestand well, the best way to do is to join the server using "net ads join" and use nss_winbind. This what I do but I only use the

On Wed, 30 Aug 2017 10:43:39 +0200 (CEST) Gaetan SLONGO <gslongo at it-optics.com> wrote: > Hi Rowland, > > > Thank you for your answer. > I think I have found a solution which could solve the issue until the > next migration step. It tested it on another server which is not > critital : > > > > > * Joining the server as a member and setup

Signed-off-by: Arthur CLEMENT <aclement at linagora.com> --- scripts/ovirt-early | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/scripts/ovirt-early b/scripts/ovirt-early index 7f7c99c..4b85102 100755 --- a/scripts/ovirt-early +++ b/scripts/ovirt-early @@ -96,6 +96,9 @@ configure_ovirt_management_nic() { >

2017-08-30 11:25 GMT+02:00 Gaetan SLONGO via samba <samba at lists.samba.org>: > Rowland, > > > Yes, I mean uidNumber and gidNumber. > I'm aware I need to work with AD but at this time I need my unix IDs (on > NSS) to keep services working. Not only for files ownership, but also for > some other services. Yeah, that's complex... > If I undestand well, the

Hi Rowland, The reason is long to explain but shortly it was about huge amount of data ~20TB stored on that server with unix user ID (comming from a S3/LDAP setup). On a DC mode it seems unix ID are in use instead of idmap id. CNAME is in added indeed. Regarding the migration as said we came from S3/LDAP and go to 4.6. The entire future structure is not fixed yet but at this time we have a

What is this??????????????????????????????????????? > -----Original Message----- > From: samba@samba.org [mailto:samba@samba.org] > Sent: Tuesday, October 05, 1999 3:06 AM > To: Bernhard Bruscha > Subject: SAMBA digest 2259 > > > SAMBA Digest 2259 > > For information on unsubscribing see http://samba.org/listproc/ > Topics covered in this issue include:

I used ddrescue to copy /dev/md1 to a disk of sufficient size, and re-ran e2fsck, and still get the error message that there's no root file system (I've tried most every superblock): # fsck -y -b 7962624 /dev/sdf fsck 1.36 (05-Feb-2005) e2fsck 1.36 (05-Feb-2005) Superblock has a bad ext3 journal (inode 8). Clear? yes *** ext3 journal has been deleted - filesystem is now ext2 only ***