search for: 2048s

Displaying 6 results from an estimated 6 matches for "2048s".

Did you mean: 2048
2010 Jul 08
2
partition offset/alignment on SAN devices.
Hey folks, I've been getting requests from the users that they want the OCFS2 filesystems aligned to 64k boundaries, however, when I began the project, the dummy of me, created the OCFS2 filesystem on top of the whole disk device (no partition) for example, one of the SAN devices would show up as /dev/dm-10, I created the filesystem using the following command: mkfs.ocfs2 -L SOMELABEL
2017 Jan 30
3
Samba-4.3 AD-DC Win7pro clients not time syncing
...Indicator: 0(no warning) Stratum: 3 (secondary reference - synced by (S)NTP) Precision: -6 (15.62ms per tick) Root Delay: 0.0313721s Root Dispersion: 0.2973346s ReferenceId: 0x84F60BE3 (source IP: 132.246.11.227) Last Successful Sync Time: 2017-01-30 11:46:22 Source: time.nrc.ca Poll Interval: 11 (2048s) And if I do this: w32tm /resync /rediscover Sending resync command to local computer The computer did not resync because no time data was available. I am afraid that I am mystified by this. Have I misconfigured something on the Samba server to account for this behaviour? I have not previously...
2017 Jan 31
0
Samba-4.3 AD-DC Win7pro clients not time syncing
...3 (secondary reference - synced by (S)NTP) > Precision: -6 (15.62ms per tick) > Root Delay: 0.0313721s > Root Dispersion: 0.2973346s > ReferenceId: 0x84F60BE3 (source IP: 132.246.11.227) > Last Successful Sync Time: 2017-01-30 11:46:22 > Source: time.nrc.ca > Poll Interval: 11 (2048s) > > And if I do this: > > w32tm /resync /rediscover > Sending resync command to local computer > The computer did not resync because no time data was available. > > I am afraid that I am mystified by this. Have I misconfigured > something on the Samba server to account...
2012 Oct 03
1
OCZ Vertex3 SSD and LSI 9211-8i (mpt2sas)
...s (populated with a bunch of 3TB SATA drives)... I'm trying to install a OCZ Vertex3 SSD on each of the two servers to do some ssd caching tests... system sees the drive, so I do the following... # parted -a min /dev/sdu parted> mklabel gpt parted> mkpart primary ext4 2048s -1s parted> q # mkfs.ext4 /dev/sdu1 and it hangs at 'Discarding device blocks: 0/58607505' which I gather is related to 'trim' aka 'discard'. iostat shows this drive as 100% busy with no activity, and 1 pending operation in the IO queue. every 30 secs or...
2007 Sep 20
8
How are alternate superblocks repaired?
Hi, Using dumpe2fs I have been able to determine that all of my alternate ext3 superblocks are corrupted (not clean), and only the primary superblock is valid, i.e. mount works and the ordered journal is applied. When the primary superblock gets flakey, i.e. the ext_attr Filesystem feature goes missing - not sure why this occurs. At this point, the mount does not apply the journal using the
2007 Dec 27
2
Failure of gvinum after panic
Hi all, I have some problems with my gvinum setup after the system panic'ed. Afterwards the system fails finding the plexes to the subdisks (or at least that is what I can understand after having searched the gvinum source code for the error string in the DMESG log..) The machine is an IBM Netfinity 5000 and the internal HW self tests does not find any errors in the hw. Luckily my root is