Displaying 4 results from an estimated 4 matches for "stor02".
2008 Oct 21
1
behavior of ALU Scheduler
...iscrepancy in open files is 1024
option alu.open-files-usage.exit-threshold 32 # Don't stop until 992
files have been written the least-used volume
option alu.stat-refresh.interval 10sec # Refresh the statistics used
for decision-making every 10 seconds
subvolumes brick1-stor01 brick1-stor02
end-volume
And I have the following directory structure visible from the client:
/mnt/gfs/test1
files:
testfile1.dat
testfile2.dat
/mnt/gfs/test2
In directory test1 I have for example files: testfile1.dat and
testfile2.dat which are physically located respectively
testfile1.dat on...
2018 Jun 25
2
Samba 4.7.1 Generating Core Dumps
...zilla pages like this:
https://bugzilla.samba.org/show_bug.cgi?id=11976
Any help will be greatly appreciated.
Kind regards,
Francis
==============================================================================================
I get these in my /var/log/messages:
==
Jun 24 03:08:45 stor02 smbd[499]: ===============================================================
Jun 24 03:08:45 stor02 smbd[499]: [2018/06/24 03:08:45.138907, 0, pid=499] ../lib/util/fault.c:79(fault_report)
Jun 24 03:08:45 stor02 smbd[499]: INTERNAL ERROR: Signal 11 in pid 499 (4.7.1)
Jun 24 03:08:45 stor02 smbd[49...
2007 Oct 15
3
Trying to recover data off SATA-to-SCSI external 2TB ARRAY
...his:
sda: Mode Sense: bf 00 00 08
SCSI device sda: drive cache: write back
sda: unknown partition table
sd 0:0:0:0: Attached scsi disk sda
I have no experience with the Smart Array Controller, just what I read the
past couple of days.
Here's how it was mounted on the HP server
/dev/cciss/c0d1 /stor02 ext3 defaults 1 1
Is there a way I can get the data off the array with my Centos server?
Any help/suggestions/tips would be greatly appreciated, I've hit a brick
wall.
2023 Feb 14
1
failed to close Bad file descriptor on file creation after using setfattr to test latency?
...volume info stor
> Volume Name: stor
> Type: Distributed-Disperse
> Volume ID: 6e94e3ce-cc15-494d-a2ad-3729e7589cdd
> Status: Started
> Snapshot Count: 0
> Number of Bricks: 2 x (2 + 1) = 6
> Transport-type: tcp
> Bricks:
> Brick1: stor01:/data/brick01a/brick
> Brick2: stor02:/data/brick02a/brick
> Brick3: stor03:/data/brick03a/brick
> Brick4: stor01:/data/brick01b/brick
> Brick5: stor02:/data/brick02b/brick
> Brick6: stor03:/data/brick03b/brick
> Options Reconfigured:
> diagnostics.count-fop-hits: on
> diagnostics.latency-measurement: on
> featu...