similar to: btrfs: failed to read chunk tree on vde1 (f18 anaconda crash)

Greetings - I had a logical volume that was running out of space on a virtual machine. I successfully expanded the LV using lvextend, and lvdisplay shows that it has been expanded. Then I went to expand the filesystem to fill the new space (# resize2fs -p /dev/vde1) and I get the results that the filesystem is already xx blocks long, nothing to do. If I do a # df -h, I can see that the

On 08/05/2015 10:23 AM, Chris Murphy wrote: > Nothing about hd0 or hd1 gets baked into the bootloader code. It's an > absolute reference to a physical drive at the moment in time the > command is made. Is that true? If I have a system with two disks, where device.map labels one as hd0 and the other as hd1, and I swap those numbers, the resulting boot sector will differ by one bit.

On Thu, 21 Jun 2018 12:02:41 -0400 (EDT) Tom Diehl via samba <samba at lists.samba.org> wrote: > Hi, > > I am trying to join a self compiled samba 4.8.2 DC to an existing > Windows domain using > https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory#Joining_the_Active_Directory_as_a_Domain_Controller > as instructions. > > The smb.conf

On Thu, 21 Jun 2018 14:32:49 -0400 (EDT) me at tdiehl.org wrote: > Hi Rowland, > > On Thu, 21 Jun 2018, Rowland Penny via samba wrote: > > > On Thu, 21 Jun 2018 12:02:41 -0400 (EDT) > > Tom Diehl via samba <samba at lists.samba.org> wrote: > > > >> Hi, > >> > >> I am trying to join a self compiled samba 4.8.2 DC to an existing >

Hi, I am trying to join a self compiled samba 4.8.2 DC to an existing Windows domain using https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory#Joining_the_Active_Directory_as_a_Domain_Controller as instructions. The smb.conf looks like the following: [global] netbios name = PHT-VDC1 realm = EXAMPLE.COM server role = active directory domain

Hi Rowland, On Thu, 21 Jun 2018, Rowland Penny via samba wrote: > On Thu, 21 Jun 2018 12:02:41 -0400 (EDT) > Tom Diehl via samba <samba at lists.samba.org> wrote: > >> Hi, >> >> I am trying to join a self compiled samba 4.8.2 DC to an existing >> Windows domain using >>

Hi, I have a new Centos 7.6 VM that I self compiled 4.10.3 and joined it to an existing samba AD domain that has 2 existing DCs. One of the existing DCs is running 4.8.7 and the other is running 4.7.7. Everything looks OK except that when I run samba-tool drs showrepl on the new DC (VDC4) I get the following output: (vdc4 pts4) # samba-tool drs showrepl Default-First-Site-Name\VDC4 DSA Options:

On Fri, 23 Oct 2020, Rowland penny via samba wrote: > On 23/10/2020 15:03, Tom Diehl via samba wrote: >> Hi, >> >> I have 2 DC's. One is running 4.10.18 and the other is running 4.11.14. >> I am planning on upgrading the 4.10.18 DC to 4.11.14 and then both up to >> 4.12r.latest. >> >> In doing this I ran samba-tool dbcheck --reindex and got

Hi, I have a Samba AD domain running 2 self compiled 4.7.3 DC's running on Centos 7. Every morning if I run wbinfo -u on DC1 I do not get any info back. I have tried reloading samba but that does not get it working. Restarting samba seems to be the only way to get it working again. DC2 continues to work normally. DC1 holds the FSMO roles and also runs bind DLZ and ISC dhcp configured per

Hi, I have 2 DC's. One is running 4.10.18 and the other is running 4.11.14. I am planning on upgrading the 4.10.18 DC to 4.11.14 and then both up to 4.12r.latest. In doing this I ran samba-tool dbcheck --reindex and got the following warning: (vdc1 pts8) # samba-tool dbcheck --reindex Re-indexing... ../../lib/ldb/ldb_key_value/ldb_kv_index.c:2413: duplicate attribute value in

Hi, I have been struggling with this OOM issue and so far nothing has helped. So we are running 10TB archive volume which stores bit more than 7M files. The problem is that due to the way we are managing this archive, we are forced to run daily "full scans" of file system to discover new uncompressed files. I know, i know, this is not optimal solution but it is as it is right now. So

Hi, I'm trying to set up a redundant DRBD system but I'm running into trouble when I try to define a volume group. The physical backing device for the drbd resource /dev/drbd0 is /dev/vdb1. The problem is that when I do a "pvs" on the command line the physical volume is shown as /dev/vdb1. So I tried the following filter in /etc/lvm/lvm.conf: filter = [

Hi Tim Andrew and Rowland, Thanks for taking the time to look into this. On Fri, 22 Jun 2018, Tim Beale via samba wrote: > Hi Tom, > > The problem here is due to fundamental implementation differences in the > way Windows and Samba store linked attributes. Your DB is likely fine > (no corruptions). That is great to hear! > During replication (i.e. the join), Windows can

Hi, I have a samba 4.7.9 DC that I am trying to remove a windows SBS dc from. In doing this I have run across several problems. For whatever reason when I try to dcpromo the windows DC it fails because it says it cannot contact the samba4 DC. I have checked replication as per https://wiki.samba.org/index.php/Verifying_the_Directory_Replication_Statuses All of the tests pass. Since we are going

hi Jones, Thanks for your reply. At 2018-01-04 19:41:27, "Richard W.M. Jones" <rjones@redhat.com> wrote: >On Thu, Jan 04, 2018 at 12:58:40PM +0800, Chen Fan wrote: >[In guest] >> python -c 'import os; s = os.statvfs ("/"); print s' >> posix.statvfs_result(f_bsize=4096, f_frsize=4096, f_blocks=5886149, >> f_bfree=4802342, f_bavail=4802342,

On Thu, Aug 6, 2015 at 3:19 PM, Chris Murphy <lists at colorremedies.com> wrote: > On Thu, Aug 6, 2015 at 2:59 PM, Gordon Messmer <gordon.messmer at gmail.com> wrote: >> On 08/05/2015 10:23 AM, Chris Murphy wrote: >>> >>> Nothing about hd0 or hd1 gets baked into the bootloader code. It's an >>> absolute reference to a physical drive at the moment

Hi Tom, The problem here is due to fundamental implementation differences in the way Windows and Samba store linked attributes. Your DB is likely fine (no corruptions). During replication (i.e. the join), Windows can sometimes send linked attributes before Samba knows about the source/target objects involved. As Andrew said, historically Samba has handled this by silently dropping these links,

On Thu, 2018-06-21 at 18:46 +0100, Rowland Penny via samba wrote: > On Thu, 21 Jun 2018 12:02:41 -0400 (EDT) > Tom Diehl via samba <samba at lists.samba.org> wrote: > > > Hi, > > > > I am trying to join a self compiled samba 4.8.2 DC to an existing > > Windows domain using > >

Hi, >Is this the machine that you cannot set the permissions on ? Yes. >If so, what is the filesystem ? Ext4 for SO and Ext4 for shared files, but I have created a pool ZFS on this last filesystem (/dev/vdb1). Dispositivo Inicializar In?cio Fim Setores Tamanho Id Tipo /dev/vda1 * 2048 62912511 62910464 30G 83 Linux Disco /dev/vdb: 5 TiB, 5497568624640 bytes,

On 16/03/2020 13:50, Marcio Demetrio Bacci wrote: > Hi, > > >Is this the machine that you cannot set the permissions on ? > Yes. > > >If so, what is the filesystem ? > Ext4 for SO and Ext4 for shared files, but I have created a pool ZFS > on this last filesystem (/dev/vdb1). > If zfs is involved in any way, you will have problems, zfs uses nfs4acls, you could try