[jira] [Created] (SPARK-46279) Support write partition values to data files

[fred liu (Jira)]

fred liu created SPARK-46279:


 Summary: Support write partition values to data files
 Key: SPARK-46279
 URL: https://issues.apache.org/jira/browse/SPARK-46279
 Project: Spark
  Issue Type: Improvement
  Components: Spark Core
Affects Versions: 4.0.0
Reporter: fred liu


Support write partition values to data files would give the flexibility to 
allow parquet files to be read correctly without relying on engine to read 
partition values from the path, and enables cases where individual parquet 
files can be copied and shared



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

[OE-core] [PATCH] glibc:drop libcidn package

[Fred Liu]

From: Fred Liu 

libcidn has been dropped since glibc 2.28

Signed-off-by: Fred Liu 
---
 meta/recipes-core/glibc/glibc-package.inc | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/meta/recipes-core/glibc/glibc-package.inc 
b/meta/recipes-core/glibc/glibc-package.inc
index 601dedb9fa..571ae7ae09 100644
--- a/meta/recipes-core/glibc/glibc-package.inc
+++ b/meta/recipes-core/glibc/glibc-package.inc
@@ -1,6 +1,6 @@
 INHIBIT_SYSROOT_STRIP = "1"
 
-PACKAGES = "${PN}-dbg catchsegv sln nscd ldconfig ldd tzcode glibc-thread-db 
${PN}-pic libcidn libmemusage malloc-debug libnss-db libsegfault 
${PN}-pcprofile libsotruss ${PN} ${PN}-utils glibc-extra-nss ${PN}-dev 
${PN}-staticdev ${PN}-doc ${PN}-src"
+PACKAGES = "${PN}-dbg catchsegv sln nscd ldconfig ldd tzcode glibc-thread-db 
${PN}-pic libmemusage malloc-debug libnss-db libsegfault ${PN}-pcprofile 
libsotruss ${PN} ${PN}-utils glibc-extra-nss ${PN}-dev ${PN}-staticdev 
${PN}-doc ${PN}-src"
 
 # The ld.so in this glibc supports the GNU_HASH
 RPROVIDES:${PN} = "eglibc rtld(GNU_HASH)"
@@ -29,7 +29,6 @@ RRECOMMENDS:${PN} = "${@bb.utils.contains('DISTRO_FEATURES', 
'ldconfig', '${MLPR
 FILES:ldconfig = "${base_sbindir}/ldconfig"
 FILES:ldd = "${bindir}/ldd"
 FILES:libsegfault = "${base_libdir}/libSegFault*"
-FILES:libcidn = "${base_libdir}/libcidn-*.so ${base_libdir}/libcidn.so.*"
 FILES:libmemusage = "${base_libdir}/libmemusage.so"
 FILES:malloc-debug = "${base_libdir}/libc_malloc_debug.so.0"
 FILES:libnss-db = "${base_libdir}/libnss_db.so.* ${base_libdir}/libnss_db-*.so 
${localstatedir}/db/Makefile ${localstatedir}/db/makedbs.sh"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156705): 
https://lists.openembedded.org/g/openembedded-core/message/156705
Mute This Topic: https://lists.openembedded.org/mt/86138216/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [X2Go-Dev] Clean processes after x2goterminate-session

[Fred Liu]

As an alternative, we may think about using system-logind to kill all user's 
processes when logout...

Thanks.

Fred

-Original Message-
From: x2go-dev  On Behalf Of Oleksandr Shneyder
Sent: 2021年8月13日 22:25
To: Ulrich Sibiller 
Cc: x2go-dev@lists.x2go.org
Subject: Re: [X2Go-Dev] Clean processes after x2goterminate-session

In my tests dbus and all processes running inside of the session having PGID of 
x2goruncommand.

Alex

Am 13.08.21 um 01:47 schrieb Ulrich Sibiller:
> Are you sure dbus does not have its own PGID?
> 
> Uli
> 
> On Thu, Aug 12, 2021 at 7:36 PM Oleksandr Shneyder 
>  wrote:
>>
>> Why we are not just saving the x2goruncommand PID in the session 
>> directory. All spawned processes will have a  PGID identical to the 
>> PID of x2goruncommand. In the x2goterminate-session we can terminate 
>> all processes with PGID identical to x2goruncommand PID:
>>
>> kill -- -X2GORUNCMD_PID
>>
>> looks simple to me and POSIX confirm. Any objections?
>>
>>
>> regards,
>> Alex
>>
>>
>> Am 11.08.21 um 04:57 schrieb Mike Gabriel:
>>> On  Di 10 Aug 2021 18:10:41 CEST, Ulrich Sibiller wrote:
>>>
 Probably it would be best to use dbus for session termination if it 
 is running.
>>>
>>> This could be one puzzle piece, indeed. Basically, we can kill 
>>> x2goruncommand and then the session manager would automatically go 
>>> into logout.
>>>
>>> However, esp. the GTK desktops (MATE, XFCE, etc.) leave many stray 
>>> processes around (e.g. gvfsd, colord, etc.). For these friends, some 
>>> more intelligence is required. Might have that in the X2Go Server 
>>> renicer code already, because Lee at those early times worked on 
>>> code that detects the complete process tree of a running desktop session.
>>>
>>> Nowadays, one could argue that cgroups are another and better 
>>> alternative. But cgroups are not available on non-Linux, so maybe a 
>>> kernel-agnostic approach is a more favourable way to go?
>>>
>>> Mike
>>
>>
>> --
>> ---
>> Oleksandr Shneyder| Email: o.shney...@phoca-gmbh.de
>> phoca GmbH| Tel. : 0911 - 14870374 0
>> Schleiermacherstr. 2  | Fax. : 0911 - 14870374 9
>> D-90491 Nürnberg  | Mobil: 0163 - 49 64 461
>>
>> Geschäftsführung: Dipl.-Inf. Oleksandr Shneyder
>>
>> Amtsgericht München   | http://www.phoca-gmbh.de
>> HRB 196 658   | http://www.x2go.org
>> USt-IdNr.: DE281977973
>> ---
>>


--
---
Oleksandr Shneyder| Email: o.shney...@phoca-gmbh.de
phoca GmbH| Tel. : 0911 - 14870374 0
Schleiermacherstr. 2  | Fax. : 0911 - 14870374 9
D-90491 Nürnberg  | Mobil: 0163 - 49 64 461

Geschäftsführung: Dipl.-Inf. Oleksandr Shneyder

Amtsgericht München   | http://www.phoca-gmbh.de
HRB 196 658   | http://www.x2go.org
USt-IdNr.: DE281977973
---



--

This email has been scanned for spam and viruses. Visit the following link to 
report this email as spam:
https://securemail.cloud-protect.net/index01.php?mod_id=11_option=logitem_id=1628864719-MZsKPgao79T4_address=fliu%40issi.com=1


___
x2go-dev mailing list
x2go-dev@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev

RE: [discuss] Sparc Hypervisor

[Fred Liu]

The majority of hypervisor for logical domain should run in SP on the mainboard.
For OS perspective, it should be some interfaces.

> -Original Message-
> From: Peter Firmstone [mailto:peter.firmst...@zeus.net.au]
> Sent: Monday, July 13, 2020 1:51 PM
> To: illumos-discuss 
> Subject: [discuss] Sparc Hypervisor
> 
> I'm setting up three logical domains on the sparc hypervisor, for building and
> developing Illumos.
> 
> I've noticed that there doesn't appear to be a logical domains manager 
> included
> with Illumos, OpenBSD fully supports the sparc hypervisor, even on the latest
> sparc processors, and it's a very small daemon and utility, so I might look at
> porting that to Illumos, but first I'll be using OpenBSD as the primary 
> control
> domain, with various illumos flavours in logical domains.
> 
> Cheers,
> 
> Peter.
> 

--
illumos: illumos-discuss
Permalink: 
https://illumos.topicbox.com/groups/discuss/T97773d1014c54504-M11bcad9c0d7939f560dea4b4
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription

Re: [slurm-users] save job comment into job completion data

[Fred Liu]

I put job completion info into a MySQL database from which I can keep a 
thorough job history. The job accounting (without -c) database can’t hold a 
long history.


发件人: slurm-users  代表 Ole Holm Nielsen 

发送时间: 星期一, 七月 6, 2020 4:01 下午
收件人: slurm-users@lists.schedmd.com
主题: Re: [slurm-users] save job comment into job completion data

On 7/5/20 5:42 PM, Fred Liu wrote:
> It looks job comment won't be saved into job completion data, for I can't see 
> it when I use sacct -c
> But I can see it when I use sacct(without -c).
>
> Is it possible to make it work?

The sacct manual page explains the -c parameter:

-c, --completion
Use job completion data instead of job accounting. The JobCompType
parameter in the slurm.conf file must be defined to a non-none option.

I'm not familiar with the job comment field, but you say that it is
printed without -c with the job accounting data. Why do you want or
expect this to work with the job completion data?


/Ole

[slurm-users] save job comment into job completion data

[Fred Liu]

Hi,

It looks job comment won't be saved into job completion data, for I can't see 
it when I use sacct -c
But I can see it when I use sacct(without -c).

Is it possible to make it work?

Thanks,

Fred

[slurm-users] epilog can't get the full OUTPUT ENVIRONMENT VARIABLES from sbatch

[Fred Liu]

Hi,

I used to have full OUTPUT ENVIRONMENT VARIABLES from sbatch.
But now I just part of them like below:
SLURM_NODELIST SLURM_JOBID SLURM_SCRIPT_CONTEXT SLURM_UID SLURM_CLUSTER_NAME 
SLURM_JOB_USER SLURM_JOB_ID SLURM_CONF SLURM_JOB_GID SLURM_JOB_UID 
SLURMD_NODENAME

I can't get SLURm_SUBMIT_HOST any more?

Any ideas?

Thanks.

Fred

How to unsubscribe

[Fred Liu]

Hi guys


-

To unsubscribe e-mail: 
user-unsubscr...@spark.apache.org<mailto:user-unsubscr...@spark.apache.org>



From: Fred Liu 
Sent: Wednesday, May 6, 2020 10:10 AM
To: user@spark.apache.org
Subject: Unsubscribe


[External E-mail]

CAUTION: This email originated from outside the organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.

Unsubscribe

[Fred Liu]

Re: [slurm-users] sacct -c not honor -M clusrername

[Fred Liu]

This way is an alternative for “-c”.
Is it possible make “-c“ work with “-M”?

Thanks.

Fred


发件人: Sudeep Narayan Banerjee 
发送时间: 星期一, 四月 27, 2020 12:33 上午
收件人: Slurm User Community List; Fred Liu
主题: Re: [slurm-users] sacct -c not honor -M clusrername


Dear Fred: should be possible

sacct --format=user,state --starttime=04/01/19 --endtime=03/31/20 | grep 
COMPLETED

Please let us know if this helps.

Thanks & Regards,
Sudeep Narayan Banerjee
System Analyst | Scientist B
Information System Technology Facility
Academic Block 5 | Room 110
Indian Institute of Technology Gandhinagar
Palaj, Gujarat 382355 INDIA

On 26/04/20 9:27 pm, Fred Liu wrote:

Hi,

Is it possible to get job completion stats per cluster?

Thanks.

Fred

[slurm-users] sacct -c not honor -M clusrername

[Fred Liu]

Hi,

Is it possible to get job completion stats per cluster?

Thanks.

Fred

[slurm-users] Is it possible to make SlurmctldPidFile in slurm.conf suport %h or %n?

[Fred Liu]

Hi,

Subject says it all.


Thanks.

Fred

[slurm-users] missing sysconfigdir in the prefix when built manually

[Fred Liu]

Hi,

I have tried manually building both 19.05 and 18.08 and found there is no 
sysconfdir(prefix/etc) in the installation path. And I have to copy it from the 
build folder.
Is it normal?

Thanks.

Fred

[jira] [Updated] (AIRFLOW-4141) Should `run_me_first` dump 3 outlets in `Lineage` document?

[Fred Liu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AIRFLOW-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Fred Liu updated AIRFLOW-4141:
--
Description: 
In the latest version(1.10.2) document, [Lineage 
chapter|https://airflow.apache.org/lineage.html], the paragraph after the 
second {color:#59afe1}Note{color}(which has blue banner) contains this line: 
... run_me_first is a BashOperator that {color:#ff}takes 3 inlets{color}: 
CAT1, CAT2, CAT3 ...

We can figure out CATx are defined as outlets instead inlets from example code 
above.

I think "run_me_first is a BashOperator that {color:#ff}dumps 3 
outlets{color}: CAT1, CAT2, CAT3" is better?

  was:
In the latest version(1.10.2) document, [Lineage 
chapter|https://airflow.apache.org/lineage.html], the paragraph after the 
second Note(which has blue banner) contains this line: ... run_me_first is a 
BashOperator that {color:#ff}takes 3 inlets{color}: CAT1, CAT2, CAT3 ...

We can figure out CATx are defined as outlets instead inlets from example code 
above.

I think "run_me_first is a BashOperator that {color:#ff}dumps 3 
outlets{color}: CAT1, CAT2, CAT3" is better?


> Should `run_me_first` dump 3 outlets in `Lineage` document?
> ---
>
> Key: AIRFLOW-4141
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4141
> Project: Apache Airflow
>  Issue Type: Bug
>  Components: docs, Documentation
>Affects Versions: 1.10.2
>Reporter: Fred Liu
>Priority: Trivial
>  Labels: easyfix
>
> In the latest version(1.10.2) document, [Lineage 
> chapter|https://airflow.apache.org/lineage.html], the paragraph after the 
> second {color:#59afe1}Note{color}(which has blue banner) contains this line: 
> ... run_me_first is a BashOperator that {color:#ff}takes 3 inlets{color}: 
> CAT1, CAT2, CAT3 ...
> We can figure out CATx are defined as outlets instead inlets from example 
> code above.
> I think "run_me_first is a BashOperator that {color:#ff}dumps 3 
> outlets{color}: CAT1, CAT2, CAT3" is better?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AIRFLOW-4141) Should `run_me_first` dump 3 outlets in `Lineage` document?

[Fred Liu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AIRFLOW-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Fred Liu updated AIRFLOW-4141:
--
Description: 
In the latest version(1.10.2) document, [Lineage 
chapter|[https://airflow.apache.org/lineage.html]], the paragraph after the 
second Note(which has blue banner) contains this line: ... run_me_first is a 
BashOperator that {color:#ff}takes 3 inlets{color}: CAT1, CAT2, CAT3 ...

We can figure out CATx are defined as outlets instead inlets from example code 
above.

I think "run_me_first is a BashOperator that {color:#ff}dumps 3 
outlets{color}: CAT1, CAT2, CAT3" is better?

  was:
In the latest version(1.10.2) document, Lineage chapter, the paragraph after 
the second Note(which has blue banner) contains this line: ... run_me_first is 
a BashOperator that {color:#ff}takes 3 inlets{color}: CAT1, CAT2, CAT3 ...

We can figure out CATx are defined as outlets instead inlets from example code 
above.

I think "run_me_first is a BashOperator that {color:#ff}dumps 3 
outlets{color}: CAT1, CAT2, CAT3" is better?


> Should `run_me_first` dump 3 outlets in `Lineage` document?
> ---
>
> Key: AIRFLOW-4141
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4141
> Project: Apache Airflow
>  Issue Type: Bug
>  Components: docs, Documentation
>Affects Versions: 1.10.2
>Reporter: Fred Liu
>Priority: Trivial
>  Labels: easyfix
>
> In the latest version(1.10.2) document, [Lineage 
> chapter|[https://airflow.apache.org/lineage.html]], the paragraph after the 
> second Note(which has blue banner) contains this line: ... run_me_first is a 
> BashOperator that {color:#ff}takes 3 inlets{color}: CAT1, CAT2, CAT3 ...
> We can figure out CATx are defined as outlets instead inlets from example 
> code above.
> I think "run_me_first is a BashOperator that {color:#ff}dumps 3 
> outlets{color}: CAT1, CAT2, CAT3" is better?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AIRFLOW-4141) Should `run_me_first` dump 3 outlets in `Lineage` document?

[Fred Liu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AIRFLOW-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Fred Liu updated AIRFLOW-4141:
--
Description: 
In the latest version(1.10.2) document, [Lineage 
chapter|https://airflow.apache.org/lineage.html], the paragraph after the 
second Note(which has blue banner) contains this line: ... run_me_first is a 
BashOperator that {color:#ff}takes 3 inlets{color}: CAT1, CAT2, CAT3 ...

We can figure out CATx are defined as outlets instead inlets from example code 
above.

I think "run_me_first is a BashOperator that {color:#ff}dumps 3 
outlets{color}: CAT1, CAT2, CAT3" is better?

  was:
In the latest version(1.10.2) document, [Lineage 
chapter|[https://airflow.apache.org/lineage.html]], the paragraph after the 
second Note(which has blue banner) contains this line: ... run_me_first is a 
BashOperator that {color:#ff}takes 3 inlets{color}: CAT1, CAT2, CAT3 ...

We can figure out CATx are defined as outlets instead inlets from example code 
above.

I think "run_me_first is a BashOperator that {color:#ff}dumps 3 
outlets{color}: CAT1, CAT2, CAT3" is better?


> Should `run_me_first` dump 3 outlets in `Lineage` document?
> ---
>
> Key: AIRFLOW-4141
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4141
> Project: Apache Airflow
>  Issue Type: Bug
>  Components: docs, Documentation
>Affects Versions: 1.10.2
>Reporter: Fred Liu
>Priority: Trivial
>  Labels: easyfix
>
> In the latest version(1.10.2) document, [Lineage 
> chapter|https://airflow.apache.org/lineage.html], the paragraph after the 
> second Note(which has blue banner) contains this line: ... run_me_first is a 
> BashOperator that {color:#ff}takes 3 inlets{color}: CAT1, CAT2, CAT3 ...
> We can figure out CATx are defined as outlets instead inlets from example 
> code above.
> I think "run_me_first is a BashOperator that {color:#ff}dumps 3 
> outlets{color}: CAT1, CAT2, CAT3" is better?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AIRFLOW-4141) Should `run_me_first` dump 3 outlets in `Lineage` document?

[Fred Liu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AIRFLOW-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Fred Liu updated AIRFLOW-4141:
--
Description: 
In the latest version(1.10.2) document, Lineage chapter, the paragraph after 
the second Note(which has blue banner) contains this line: ... run_me_first is 
a BashOperator that {color:#ff}takes 3 inlets{color}: CAT1, CAT2, CAT3 ...

We can figure out CATx are defined as outlets instead inlets from example code 
above.

I think "run_me_first is a BashOperator that {color:#ff}dumps 3 
outlets{color}: CAT1, CAT2, CAT3" is better?

  was:
In latest version document, Lineage chapter, the paragraph after the second 
Note(which has blue banner) contains this line: ... run_me_first is a 
BashOperator that {color:#FF}takes 3 inlets{color}: CAT1, CAT2, CAT3 ...

We can figure out CATx are defined as outlets instead inlets from example code 
above.

I think "run_me_first is a BashOperator that {color:#FF}dumps 3 
outlets{color}: CAT1, CAT2, CAT3" is better?


> Should `run_me_first` dump 3 outlets in `Lineage` document?
> ---
>
> Key: AIRFLOW-4141
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4141
> Project: Apache Airflow
>  Issue Type: Bug
>  Components: docs, Documentation
>Affects Versions: 1.10.2
>Reporter: Fred Liu
>Priority: Trivial
>  Labels: easyfix
>
> In the latest version(1.10.2) document, Lineage chapter, the paragraph after 
> the second Note(which has blue banner) contains this line: ... run_me_first 
> is a BashOperator that {color:#ff}takes 3 inlets{color}: CAT1, CAT2, CAT3 
> ...
> We can figure out CATx are defined as outlets instead inlets from example 
> code above.
> I think "run_me_first is a BashOperator that {color:#ff}dumps 3 
> outlets{color}: CAT1, CAT2, CAT3" is better?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AIRFLOW-4141) Should `run_me_first` dump 3 outlets in `Lineage` document?

[Fred Liu (JIRA)]

Fred Liu created AIRFLOW-4141:
-

 Summary: Should `run_me_first` dump 3 outlets in `Lineage` 
document?
 Key: AIRFLOW-4141
 URL: https://issues.apache.org/jira/browse/AIRFLOW-4141
 Project: Apache Airflow
  Issue Type: Bug
  Components: docs, Documentation
Affects Versions: 1.10.2
Reporter: Fred Liu


In latest version document, Lineage chapter, the paragraph after the second 
Note(which has blue banner) contains this line: ... run_me_first is a 
BashOperator that {color:#FF}takes 3 inlets{color}: CAT1, CAT2, CAT3 ...

We can figure out CATx are defined as outlets instead inlets from example code 
above.

I think "run_me_first is a BashOperator that {color:#FF}dumps 3 
outlets{color}: CAT1, CAT2, CAT3" is better?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Your removal from the SCIENTIFIC-LINUX-USERS list

[Fred Liu]

I lost the mails from 11/12 to 11/15 ...
Fred Liu  于2018年11月16日周五 下午6:41写道：
>
> What is this?
>
> -- Forwarded message -
> From: Fermilab LISTSERV Server (16.0) 
> Date: 2018年11月15日周四 下午2:02
> Subject: Your removal from the SCIENTIFIC-LINUX-USERS list
> To: 
>
>
>
> Thu, 15 Nov 2018 00:02:23
>
> You have been automatically  removed from the SCIENTIFIC-LINUX-USERS list
> (Mailing  list for  Scientific  Linux  users worldwide)  as  a result  of
> repeated delivery error reports from  your mail system. This decision was
> based on  the list's automatic error  monitoring policy and has  not been
> reviewed or otherwise confirmed by a person. If you receive this message,
> then it  means that something is  wrong. While you are  obviously able to
> receive mail,  your mail  system has been  regularly reporting  that your
> account did not  exist, or that you were otherwise  permanently unable to
> receive mail. Here is some information  that may assist you or your local
> help desk in determining the cause of the problem:
>
> - The failing address is fred.f...@gmail.com.
>
> - The first error was reported on 2018-09-04.
>
> - Since then, a total of 7 delivery errors have been received.
>
> -  The last  reported  error  was: 5.1.8  550  5.1.8  Access denied,  bad
> outboundsender. Formoreinformationplease goto
> https://urldefense.proofpoint.com/v2/url?u=http-3A__go.microsoft.com_fwlink_-3FLinkId-3D526653=DwIFaQ=gRgGjJ3BkIsb5y6s49QqsA=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A=2eiNF49aI3l4On-amZwE_VfT8INXz4Pu6j7ka2QY_JU=kEnPyA_eYCgoMC99GPlHKTN2L6wAq2LfsPhHwaLAO7Q=.
> S(8991)
> [DM2PR09MB0399.namprd09.prod.outlook.com]
> [BL2PR09CA0020.namprd09.prod.outlook.com] [BN1AFFO11FD027.protection.gbl]
>
> Please do  not ignore  this message.  While you  can re-subscribe  to the
> list,  it is  important  for you  to  report this  problem  to your  mail
> administrator so that  it can be solved. This problem  is not specific to
> the SCIENTIFIC-LINUX-USERS  list and may  also affect your  private mail.
> This  means that  you may  have lost  some private  mail as  well. Anyone
> trying to write to you during the same time frame might have received the
> same errors for the same reason.

Fwd: Your removal from the SCIENTIFIC-LINUX-USERS list

[Fred Liu]

What is this?

-- Forwarded message -
From: Fermilab LISTSERV Server (16.0) 
Date: 2018年11月15日周四 下午2:02
Subject: Your removal from the SCIENTIFIC-LINUX-USERS list
To: 



Thu, 15 Nov 2018 00:02:23

You have been automatically  removed from the SCIENTIFIC-LINUX-USERS list
(Mailing  list for  Scientific  Linux  users worldwide)  as  a result  of
repeated delivery error reports from  your mail system. This decision was
based on  the list's automatic error  monitoring policy and has  not been
reviewed or otherwise confirmed by a person. If you receive this message,
then it  means that something is  wrong. While you are  obviously able to
receive mail,  your mail  system has been  regularly reporting  that your
account did not  exist, or that you were otherwise  permanently unable to
receive mail. Here is some information  that may assist you or your local
help desk in determining the cause of the problem:

- The failing address is fred.f...@gmail.com.

- The first error was reported on 2018-09-04.

- Since then, a total of 7 delivery errors have been received.

-  The last  reported  error  was: 5.1.8  550  5.1.8  Access denied,  bad
outboundsender. Formoreinformationplease goto
https://urldefense.proofpoint.com/v2/url?u=http-3A__go.microsoft.com_fwlink_-3FLinkId-3D526653=DwIFaQ=gRgGjJ3BkIsb5y6s49QqsA=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A=rUo3B0qf2Uw-s4RhNyXji2xFzpU_AIe6DbvuonXIov0=a-t6j2RMLbvHVxTf4D4B80ynBqAIynmqz5jNQu71J-I=.
S(8991)
[DM2PR09MB0399.namprd09.prod.outlook.com]
[BL2PR09CA0020.namprd09.prod.outlook.com] [BN1AFFO11FD027.protection.gbl]

Please do  not ignore  this message.  While you  can re-subscribe  to the
list,  it is  important  for you  to  report this  problem  to your  mail
administrator so that  it can be solved. This problem  is not specific to
the SCIENTIFIC-LINUX-USERS  list and may  also affect your  private mail.
This  means that  you may  have lost  some private  mail as  well. Anyone
trying to write to you during the same time frame might have received the
same errors for the same reason.

RE: kicked off the list via Office 365?

[Fred Liu]

me too

> -Original Message-
> From: owner-scientific-linux-us...@listserv.fnal.gov
> [mailto:owner-scientific-linux-us...@listserv.fnal.gov] On Behalf Of Howard,
> Chris
> Sent: 星期四, 十一月 15, 2018 23:39
> To: SCIENTIFIC-LINUX-USERS@fnal.gov
> Subject: kicked off the list via Office 365?
> 
> FYI
> 
> I received a kicked-off-the-list message which seems to indicate that either 
> the
> listserv or people being relayed through the listserv were falling afoul of 
> Office
> 365 spam-control on my end, which gave me too many bounces and hence,
> kicked off.

[smartos-discuss] avx2

[Fred Liu]

Hi,

I know qemu version on smartos is out of date. So kvm vm won’t have avx2 
instruction set by now. Will bhyve vm have them?

Thanks.

Fred



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125
Powered by Listbox: https://www.listbox.com

Re: [smartos-discuss] Smartos bhyve support on AMD Sun Fire X4140

[Fred Liu]

Even Ryzen-based ?

Thanks

Fred




On Wed, Jul 4, 2018 at 1:56 AM +0800, "Jorge Schrauwen" 
mailto:sjorge...@blackdot.be>> wrote:

Yeah, no support as of yet. Although there does seem to be some interest in 
adding it eventually. (Based on conversations on IRC)

July 3, 2018 6:38 PM, "J?n Poctavek" 
mailto:jan.pocta...@erigones.com?to=%22J%C3%A1n%20Poctavek%22%20>>
 wrote:

Hi,

Just to be sure - so no AMD support again?
Jan

On 3. 7. 2018 11:42, Jorge Schrauwen wrote:
For now bhyve support on SmartOS requires VMX and EPT to work.
So older intel CPU without EPT or AMD CPU that use SVM are not support.

Regards

Jorge

July 3, 2018 11:15 AM, "Paolo Marcheschi" 
mailto:paolo.marches...@ftgm.it?to=%22paolo%20marcheschi%22%20%3cpaolo.marches...@ftgm.it%3E>>
 wrote:

Hi

Today I tried to run a bhyve VM on the latest Smartos:

SunOS 5.11 joyent_20180629T143106Z i86pc i386 i86pc

The server is an AMD Opteron Sun Fire X4140 :

psrinfo -vp The physical processor has 6 virtual processors (0-5) x86 
(AuthenticAMD 100F80 family 16 model 8 step 0 clock 2200 MHz) Six-Core AMD 
Opteron(tm) Processor 2427 [ Socket: F(1207) ] The physical processor has 6 
virtual processors (6-11) x86 (AuthenticAMD 100F80 family 16 model 8 step 0 
clock 2200 MHz) Six-Core AMD Opteron(tm) Processor 2427 [ Socket: F(1207) ]

when I try to create a bhyve VM I get:
#vmadm create -f centos.json
Bhyve not supported
Why ?
Thank you
Paolo




smartos-discuss | Archives 
| Modify Your Subscription   
[https://www.listbox.com/images/listbox-logo-small.png96494be.png?uri=aHR0cHM6Ly93d3cubGlzdGJveC5jb20vaW1hZ2VzL2xpc3Rib3gtbG9nby1zbWFsbC5wbmc]
 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] Migration KVM to Bhyve - Performance Issues

[Fred Liu]

> -Original Message-
> From: Brian Bennett [mailto:brian.benn...@joyent.com]
> Sent: 星期日, 五月 27, 2018 2:14
> To: smartos-discuss@lists.smartos.org
> Subject: Re: [smartos-discuss] Migration KVM to Bhyve - Performance Issues
> 
> On May 26, 2018, at 6:57 AM, Humberto Ramirez   > wrote:
> 
> 
> 
>   Assuming some of this steps can be scripted is there plans for a "KVM  
> to
> Bhyve" conversion utility?
> 
> 
> 
> Joyent is looking into kvm->bhyve conversion being part of the product. It's
> certainly something we'd like to do, but there's a number of other bhyve 
> things
> that are being worked on first, and there are a number of architectural
> decisions that were changed with bhyve that makes direct conversion not quite
> so straight forward. In particular, the dataset layout has changed and kvm
> includes a mini dhcp server for networking, 

Any more details or source code about this mini dhcp server? Is it configurable?


whereas bhyve will consume the
> network settings using instance metadata.
> 
> --
> Brian Bennett
> Systems Engineer, Cloud Operations
> Joyent, Inc. | www.joyent.com 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125
Powered by Listbox: http://www.listbox.com

[EPEL-devel] Re: incompatibility issue for mate-desktop

[Fred Liu]

pulp is really good except it is sort of heavy for small deployment. The tricky 
part is the time to freeze or branch. Can it branch via every EPEL update? What 
is the update mode for EPEL – randomly update with individual package or 
regular update with bunch of packages as whole? I assume the former.

From: Trey Dockendorf [mailto:treyd...@gmail.com]
Sent: 星期四, 四月 26, 2018 2:31
To: EPEL Development List
Subject: [EPEL-devel] Re: incompatibility issue for mate-desktop

Could look into Pulp, https://pulpproject.org/, which I've used in the past to 
freeze a copy of EPEL locally to avoid updates when I needed to keep systems 
frozen on specific minor releases of CentOS.  Pulp allowed me to efficiently 
create multiple copies of the EPEL repos that I could point my various systems 
at, some getting latest and some getting frozen.

- Trey

On Wed, Apr 25, 2018 at 2:07 PM, Fred Liu 
<fred_...@issi.com<mailto:fred_...@issi.com>> wrote:
Totally agree. And quick iteration is the nut of Linux especially for personal 
usage. But in enterprise scenario, there’s normalization. That is why LTS and 
subscription make sense. I am not gonna troll in 《cathedral and bazaar》. ^:^

Originally I am thinking about downloading rpm packages from EPEL and merging 
these packages into 7.3’s ISO file. But it seems rebuilding from source is also 
a good approach!  I will try this way later.

Little bit off-topic, the main purpose to play OL7.5 is to taste kslice and 
dtrace though UEK can be installed/built on SL too. If there is feasible 
hot-kernel-patching, quick iteration will dominate more in enterprise 
on-premise demand.



On Thu, Apr 26, 2018 at 1:27 AM +0800, "Manuel Wolfshant" 
<wo...@nobugconsulting.ro<mailto:wo...@nobugconsulting.ro>> wrote:

On April 25, 2018 6:46:44 PM GMT+03:00, Fred Liu  wrote:

>OK. Then I am thinking about brunch and merge into OS’s iso once there

>is

>package update in EPEL.



EPEL always tracks the latest RHEL minor release. If you decide to ignore  all 
the security risks associated with the lack of updates and prefer to freeze 
your system at an old(er) minor release of RHEL (or clone) you will need to 
grab the sources of the updated EPEL packages and rebuild them youself for your 
environment. The EPEL project lacks the resources needed for such a task.



And BTW , you can install the latest EPEL packages on OEL 7.5 because it has 
the updated packages that came with RHEL 7.5 (and which, incidentally, will 
land in the CentOS world very very soon as well).



If you really must use an old minor release you probably should subscribe to 
RHEL EUS. This will ensure a better approach to the security aspect but will 
not solve your issues regarding the  compatibility with EPEL. And pretty 
please, do not imagine that a system not facing the Internet is safe. Stuxnet 
infected air gapped computers.







manuel







>

>Thanks.

>

>Fred

>

>Stephen John Smoogen 于2018年4月25日 周三下午11:40写道：

>

>> On 25 April 2018 at 10:31, Fred Liu  wrote:

>> > It is understandable. But why not keep the old versions in the very

>same

>> > repo? yum is capable of matching the them with different OSes.

>> >

>>

>> No it isn't. Yum will upgrade you to the latest version in the

>> repository so there would need to be a 7.3 tree and yum would have to

>> point to it. That takes a lot of work on our side and not a lot of

>> people have been interested in doing the work.

>>

>> > Thanks.

>> >

>> > Fred

>> >

>> >

>> >

>> >

>> > On Wed, Apr 25, 2018 at 10:27 PM +0800, "Pat Riehecky" <

>> riehe...@fnal.gov<mailto:riehe...@fnal.gov>>

>> > wrote:

>> >

>> >> EPEL tracks the latest RHEL release.  There are a number of fixes

>in 7.4

>> >> and 7.5 that are really worth it.

>> >>

>> >> Pat

>> >>

>> >> On 04/25/2018 09:09 AM, Fred Liu wrote:

>> >>

>> >> So abandon SL7.3? Does it mean EPEL doesn’t have consistent

>> compatibility?

>> >>

>> >> Thanks.

>> >>

>> >> Fred

>> >>

>> >>

>> >>

>> >>

>> >> On Wed, Apr 25, 2018 at 9:57 PM +0800, "Pat Riehecky" <

>> riehe...@fnal.gov<mailto:riehe...@fnal.gov>>

>> >> wrote:

>> >>

>> >>> I would recommend updating to SL 7.4

>> >>>

>> >>> Pat

>> >>>

>> >>> On 04/25/2018 08:37 AM, Fred Liu wrote:

>> >>> > Hi,

>> >>> >

>> >>> > I used to successfully install mate-desktop on SL7.3 by EPEL7.

>But

>>

[EPEL-devel] Re: incompatibility issue for mate-desktop

[Fred Liu]

Totally agree. And quick iteration is the nut of Linux especially for personal 
usage. But in enterprise scenario, there's normalization. That is why LTS and 
subscription make sense. I am not gonna troll in ?cathedral and bazaar?. ^:^

Originally I am thinking about downloading rpm packages from EPEL and merging 
these packages into 7.3's ISO file. But it seems rebuilding from source is also 
a good approach!  I will try this way later.

Little bit off-topic, the main purpose to play OL7.5 is to taste kslice and 
dtrace though UEK can be installed/built on SL too. If there is feasible 
hot-kernel-patching, quick iteration will dominate more in enterprise 
on-premise demand.




On Thu, Apr 26, 2018 at 1:27 AM +0800, "Manuel Wolfshant" 
<wo...@nobugconsulting.ro<mailto:wo...@nobugconsulting.ro>> wrote:


On April 25, 2018 6:46:44 PM GMT+03:00, Fred Liu  wrote:
>OK. Then I am thinking about brunch and merge into OS's iso once there
>is
>package update in EPEL.

EPEL always tracks the latest RHEL minor release. If you decide to ignore  all 
the security risks associated with the lack of updates and prefer to freeze 
your system at an old(er) minor release of RHEL (or clone) you will need to 
grab the sources of the updated EPEL packages and rebuild them youself for your 
environment. The EPEL project lacks the resources needed for such a task.

And BTW , you can install the latest EPEL packages on OEL 7.5 because it has 
the updated packages that came with RHEL 7.5 (and which, incidentally, will 
land in the CentOS world very very soon as well).

If you really must use an old minor release you probably should subscribe to 
RHEL EUS. This will ensure a better approach to the security aspect but will 
not solve your issues regarding the  compatibility with EPEL. And pretty 
please, do not imagine that a system not facing the Internet is safe. Stuxnet 
infected air gapped computers.



manuel



>
>Thanks.
>
>Fred
>
>Stephen John Smoogen ?2018?4?25? ????11:40???
>
>> On 25 April 2018 at 10:31, Fred Liu  wrote:
>> > It is understandable. But why not keep the old versions in the very
>same
>> > repo? yum is capable of matching the them with different OSes.
>> >
>>
>> No it isn't. Yum will upgrade you to the latest version in the
>> repository so there would need to be a 7.3 tree and yum would have to
>> point to it. That takes a lot of work on our side and not a lot of
>> people have been interested in doing the work.
>>
>> > Thanks.
>> >
>> > Fred
>> >
>> >
>> >
>> >
>> > On Wed, Apr 25, 2018 at 10:27 PM +0800, "Pat Riehecky" <
>> riehe...@fnal.gov>
>> > wrote:
>> >
>> >> EPEL tracks the latest RHEL release.  There are a number of fixes
>in 7.4
>> >> and 7.5 that are really worth it.
>> >>
>> >> Pat
>> >>
>> >> On 04/25/2018 09:09 AM, Fred Liu wrote:
>> >>
>> >> So abandon SL7.3? Does it mean EPEL doesn't have consistent
>> compatibility?
>> >>
>> >> Thanks.
>> >>
>> >> Fred
>> >>
>> >>
>> >>
>> >>
>> >> On Wed, Apr 25, 2018 at 9:57 PM +0800, "Pat Riehecky" <
>> riehe...@fnal.gov>
>> >> wrote:
>> >>
>> >>> I would recommend updating to SL 7.4
>> >>>
>> >>> Pat
>> >>>
>> >>> On 04/25/2018 08:37 AM, Fred Liu wrote:
>> >>> > Hi,
>> >>> >
>> >>> > I used to successfully install mate-desktop on SL7.3 by EPEL7.
>But
>> >>> > today, when I tried again, I saw some incompatibility
>> >>> > issues(glib2,gtk3+,etc). And I can successfully install it on
>OL7.5.
>> >>> > Is normal? From my understanding, EPEL7 should work in both
>> >>> > OSes.
>> >>> >
>> >>> > Any ideas?
>> >>> >
>> >>> >
>> >>> > Thanks.
>> >>> >
>> >>> >
>> >>> > Fred
>> >>> > ___
>> >>> > epel-devel mailing list -- epel-devel@lists.fedoraproject.org
>> >>> > To unsubscribe send an email to
>> >>> > epel-devel-le...@lists.fedoraproject.org
>> >>>
>> >>> --
>> >>> Pat Riehecky
>> >>>
>> >>> Fermi National Accelerator Laboratory
>> >>> www.fnal.gov
>> >>> www.scientif

[EPEL-devel] Re: incompatibility issue for mate-desktop

[Fred Liu]

OK. Then I am thinking about brunch and merge into OS’s iso once there is
package update in EPEL.

Thanks.

Fred

Stephen John Smoogen <smo...@gmail.com>于2018年4月25日 周三下午11:40写道：

> On 25 April 2018 at 10:31, Fred Liu <fred_...@issi.com> wrote:
> > It is understandable. But why not keep the old versions in the very same
> > repo? yum is capable of matching the them with different OSes.
> >
>
> No it isn't. Yum will upgrade you to the latest version in the
> repository so there would need to be a 7.3 tree and yum would have to
> point to it. That takes a lot of work on our side and not a lot of
> people have been interested in doing the work.
>
> > Thanks.
> >
> > Fred
> >
> >
> >
> >
> > On Wed, Apr 25, 2018 at 10:27 PM +0800, "Pat Riehecky" <
> riehe...@fnal.gov>
> > wrote:
> >
> >> EPEL tracks the latest RHEL release.  There are a number of fixes in 7.4
> >> and 7.5 that are really worth it.
> >>
> >> Pat
> >>
> >> On 04/25/2018 09:09 AM, Fred Liu wrote:
> >>
> >> So abandon SL7.3? Does it mean EPEL doesn’t have consistent
> compatibility?
> >>
> >> Thanks.
> >>
> >> Fred
> >>
> >>
> >>
> >>
> >> On Wed, Apr 25, 2018 at 9:57 PM +0800, "Pat Riehecky" <
> riehe...@fnal.gov>
> >> wrote:
> >>
> >>> I would recommend updating to SL 7.4
> >>>
> >>> Pat
> >>>
> >>> On 04/25/2018 08:37 AM, Fred Liu wrote:
> >>> > Hi,
> >>> >
> >>> > I used to successfully install mate-desktop on SL7.3 by EPEL7. But
> >>> > today, when I tried again, I saw some incompatibility
> >>> > issues(glib2,gtk3+,etc). And I can successfully install it on OL7.5.
> >>> > Is normal? From my understanding, EPEL7 should work in both
> >>> > OSes.
> >>> >
> >>> > Any ideas?
> >>> >
> >>> >
> >>> > Thanks.
> >>> >
> >>> >
> >>> > Fred
> >>> > ___
> >>> > epel-devel mailing list -- epel-devel@lists.fedoraproject.org
> >>> > To unsubscribe send an email to
> >>> > epel-devel-le...@lists.fedoraproject.org
> >>>
> >>> --
> >>> Pat Riehecky
> >>>
> >>> Fermi National Accelerator Laboratory
> >>> www.fnal.gov
> >>> www.scientificlinux.org
> >>> ___
> >>> epel-devel mailing list -- epel-devel@lists.fedoraproject.org
> >>> To unsubscribe send an email to
> epel-devel-le...@lists.fedoraproject.org
> >>
> >>
> >>
> >> ___
> >> epel-devel mailing list -- epel-devel@lists.fedoraproject.org
> >> To unsubscribe send an email to
> epel-devel-le...@lists.fedoraproject.org
> >>
> >>
> >> --
> >> Pat Riehecky
> >>
> >> Fermi National Accelerator Laboratory
> >> www.fnal.gov
> >> www.scientificlinux.org
> >
> >
> > ___
> > epel-devel mailing list -- epel-devel@lists.fedoraproject.org
> > To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
> >
>
>
>
> --
> Stephen J Smoogen.
> ___
> epel-devel mailing list -- epel-devel@lists.fedoraproject.org
> To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
>
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org

[EPEL-devel] Re: incompatibility issue for mate-desktop

[Fred Liu]

It is understandable. But why not keep the old versions in the very same repo? 
yum is capable of matching the them with different OSes.

Thanks.

Fred




On Wed, Apr 25, 2018 at 10:27 PM +0800, "Pat Riehecky" 
<riehe...@fnal.gov<mailto:riehe...@fnal.gov>> wrote:

EPEL tracks the latest RHEL release.  There are a number of fixes in 7.4 and 
7.5 that are really worth it.

Pat

On 04/25/2018 09:09 AM, Fred Liu wrote:
So abandon SL7.3? Does it mean EPEL doesn't have consistent compatibility?

Thanks.

Fred




On Wed, Apr 25, 2018 at 9:57 PM +0800, "Pat Riehecky" 
<riehe...@fnal.gov<mailto:riehe...@fnal.gov>> wrote:


I would recommend updating to SL 7.4

Pat

On 04/25/2018 08:37 AM, Fred Liu wrote:
> Hi,
>
> I used to successfully install mate-desktop on SL7.3 by EPEL7. But
> today, when I tried again, I saw some incompatibility
> issues(glib2,gtk3+,etc). And I can successfully install it on OL7.5.
> Is normal? From my understanding, EPEL7 should work in both
> OSes.
>
> Any ideas?
>
>
> Thanks.
>
>
> Fred
> ___
> epel-devel mailing list -- 
> epel-devel@lists.fedoraproject.org<mailto:epel-devel@lists.fedoraproject.org>
> To unsubscribe send an email to 
> epel-devel-le...@lists.fedoraproject.org<mailto:epel-devel-le...@lists.fedoraproject.org>

--
Pat Riehecky

Fermi National Accelerator Laboratory
www.fnal.gov<http://www.fnal.gov>
www.scientificlinux.org<http://www.scientificlinux.org>
___
epel-devel mailing list -- 
epel-devel@lists.fedoraproject.org<mailto:epel-devel@lists.fedoraproject.org>
To unsubscribe send an email to 
epel-devel-le...@lists.fedoraproject.org<mailto:epel-devel-le...@lists.fedoraproject.org>




___
epel-devel mailing list -- 
epel-devel@lists.fedoraproject.org<mailto:epel-devel@lists.fedoraproject.org>
To unsubscribe send an email to 
epel-devel-le...@lists.fedoraproject.org<mailto:epel-devel-le...@lists.fedoraproject.org>



--
Pat Riehecky

Fermi National Accelerator Laboratory
www.fnal.gov<http://www.fnal.gov>
www.scientificlinux.org<http://www.scientificlinux.org>
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org

[EPEL-devel] Re: incompatibility issue for mate-desktop

[Fred Liu]

So abandon SL7.3? Does it mean EPEL doesn't have consistent compatibility?

Thanks.

Fred




On Wed, Apr 25, 2018 at 9:57 PM +0800, "Pat Riehecky" 
<riehe...@fnal.gov<mailto:riehe...@fnal.gov>> wrote:


I would recommend updating to SL 7.4

Pat

On 04/25/2018 08:37 AM, Fred Liu wrote:
> Hi,
>
> I used to successfully install mate-desktop on SL7.3 by EPEL7. But
> today, when I tried again, I saw some incompatibility
> issues(glib2,gtk3+,etc). And I can successfully install it on OL7.5.
> Is normal? From my understanding, EPEL7 should work in both
> OSes.
>
> Any ideas?
>
>
> Thanks.
>
>
> Fred
> ___
> epel-devel mailing list -- epel-devel@lists.fedoraproject.org
> To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org

--
Pat Riehecky

Fermi National Accelerator Laboratory
www.fnal.gov
www.scientificlinux.org
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org

___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org

[EPEL-devel] incompatibility issue for mate-desktop

[Fred Liu]

Hi,

I used to successfully install mate-desktop on SL7.3 by EPEL7. But
today, when I tried again, I saw some incompatibility
issues(glib2,gtk3+,etc). And I can successfully install it on OL7.5.
Is normal? From my understanding, EPEL7 should work in both
OSes.

Any ideas?


Thanks.


Fred
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org

Re: [smartos-discuss] add device to OS/LX zone

[Fred Liu]

But creating ufs failed. It is just to emulate application's access on real 
hardware. I don't believe it will work as a raw block device.

Thanks.

Fred




On Tue, Feb 27, 2018 at 9:09 PM +0800, "Jorge Schrauwen" 
<sjorge...@blackdot.be<mailto:sjorge...@blackdot.be>> wrote:


In your example you called newfs, which creates a new UFS file system.



I think if you don't create a filesystem on it and use it as a raw block device 
it should just work.
This is what qemu does when running inside a KVM branded zone.

Regards

Jorge

On 2018-02-27 14:05, Fred Liu wrote:

Actually?we need access the real hardware not the file system. There is some 
database software which claims having performance optimization on real 
hardware. I notice that we can tune zfs rec block size in vm, maybe that is 
another idea. Anyone tuned?

Thanks!

Fred





On Tue, Feb 27, 2018 at 8:45 PM +0800, "Jorge Schrauwen" 
<sjorge...@blackdot.be<mailto:sjorge...@blackdot.be>> wrote:


Hi,

You probably want to set fs_allowed so it includes the filesystem you
are trying to create on it.

(from man vmadm)
fs_allowed:

This option allows you to specify filesystem types this zone
is allowed
to mount.  For example on a zone for building SmartOS you
probably want
to set this to: "ufs,pcfs,tmpfs".  To unset this property,
set the
value to the empty string.

type: string (comma separated list of filesystem types)
vmtype: OS
listable: no
create: yes
update: yes (requires zone reboot to take effect)

Regards

Jorge


On 2018-02-27 13:41, Fred Liu wrote:
> Hi,
> 
> For I have no spare hardware(disk), I have tried adding zvol to OS/LX
> zone. But it looks likes not working as the document.
> zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8:device> set
> match=/dev/zvol/rdsk/zones/device
> zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8:device> end
> zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8> verify
> zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8> exit
> 
> [root@pluto /zones/build]# zlogin f58e8c87-eb04-ea48-bf23-9b7be32515b8
> [Connected to zone 'f58e8c87-eb04-ea48-bf23-9b7be32515b8' pts/6]
> Last login: Tue Feb 27 20:25:02 on pts/6
>__.   .
>  _|  |_  | .-. .  . .-. :--. |-
> |__| ;|   ||  |(.-' |  | |
>   |__|   `--'  `-' `;-| `-' '  ' `-'
>/  ; Instance (base-multiarch-lts 15.4.0)
>`-'  https://docs.joyent.com/images/smartos/base
> 
> [root@f58e8c87-eb04-ea48-bf23-9b7be32515b8 ~]# ls -la
> /dev/zvol/rdsk/zones/device
> crw--- 1 root sys 90, 26 Feb 27 20:35 /dev/zvol/rdsk/zones/device
> [root@f58e8c87-eb04-ea48-bf23-9b7be32515b8 ~]# newfs
> /dev/zvol/rdsk/zones/device
> newfs: construct a new file system /dev/zvol/rdsk/zones/device: (y/n)?
> y
> can't check mount point; can't stat
> 
> Will the real hardware be different?
> 
> I also tried adding zvol to zones on solaris11.2. It works well.
> device:
>   match not specified
>   storage.template:
> dev:/dev/zvol/dsk/%{global-rootzpool}/VARSHARE/zones/%{zonename}/disk%{id}
>   storage: dev:/dev/zvol/dsk/rpool/VARSHARE/zones/kz01/disk0
>   0
>   bootpri: 0
> device:
>   match not specified
>   storage: dev:/dev/zvol/dsk/tank/device
>   2
>   bootpri: 2
> capped-memory:
>   physical: 2G
> keysource:
>   raw redacted
> zonecfg:kz01>
> 
> root@kz01:~# format
> Searching for disks...done
> 
> AVAILABLE DISK SELECTIONS:
> . c1d0
>   /kz-devices@ff/disk@0
>   c1d2
>   /kz-devices@ff/disk@2
> Specify disk (enter its number): ^C
> root@kz01:~# zpool create test1 c1d2
> root@kz01:~# zpool list
> NAMESIZE  ALLOC   FREE  CAP  DEDUP  HEALTH  ALTROOT
> rpool  15.9G  5.35G  10.5G  33%  1.00x  ONLINE  -
> test1  9.94G   124K  9.94G   0%  1.00x  ONLINE  -
> root@kz01:~#
> 
> Thinking little bit more, for we already can add zvol to kvm zone, it
> should not be very hard to realize in OS/LX zone.
> 
> Thanks.
> 
> Fred
> 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] add device to OS/LX zone

[Fred Liu]

Actually?we need access the real hardware not the file system. There is some 
database software which claims having performance optimization on real 
hardware. I notice that we can tune zfs rec block size in vm, maybe that is 
another idea. Anyone tuned?

Thanks!

Fred




On Tue, Feb 27, 2018 at 8:45 PM +0800, "Jorge Schrauwen" 
<sjorge...@blackdot.be<mailto:sjorge...@blackdot.be>> wrote:


Hi,

You probably want to set fs_allowed so it includes the filesystem you
are trying to create on it.

(from man vmadm)
fs_allowed:

This option allows you to specify filesystem types this zone
is allowed
to mount.  For example on a zone for building SmartOS you
probably want
to set this to: "ufs,pcfs,tmpfs".  To unset this property,
set the
value to the empty string.

type: string (comma separated list of filesystem types)
vmtype: OS
listable: no
create: yes
update: yes (requires zone reboot to take effect)

Regards

Jorge


On 2018-02-27 13:41, Fred Liu wrote:
> Hi,
> 
> For I have no spare hardware(disk), I have tried adding zvol to OS/LX
> zone. But it looks likes not working as the document.
> zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8:device> set
> match=/dev/zvol/rdsk/zones/device
> zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8:device> end
> zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8> verify
> zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8> exit
> 
> [root@pluto /zones/build]# zlogin f58e8c87-eb04-ea48-bf23-9b7be32515b8
> [Connected to zone 'f58e8c87-eb04-ea48-bf23-9b7be32515b8' pts/6]
> Last login: Tue Feb 27 20:25:02 on pts/6
>__.   .
>  _|  |_  | .-. .  . .-. :--. |-
> |__| ;|   ||  |(.-' |  | |
>   |__|   `--'  `-' `;-| `-' '  ' `-'
>/  ; Instance (base-multiarch-lts 15.4.0)
>`-'  https://docs.joyent.com/images/smartos/base
> 
> [root@f58e8c87-eb04-ea48-bf23-9b7be32515b8 ~]# ls -la
> /dev/zvol/rdsk/zones/device
> crw--- 1 root sys 90, 26 Feb 27 20:35 /dev/zvol/rdsk/zones/device
> [root@f58e8c87-eb04-ea48-bf23-9b7be32515b8 ~]# newfs
> /dev/zvol/rdsk/zones/device
> newfs: construct a new file system /dev/zvol/rdsk/zones/device: (y/n)?
> y
> can't check mount point; can't stat
> 
> Will the real hardware be different?
> 
> I also tried adding zvol to zones on solaris11.2. It works well.
> device:
>   match not specified
>   storage.template:
> dev:/dev/zvol/dsk/%{global-rootzpool}/VARSHARE/zones/%{zonename}/disk%{id}
>   storage: dev:/dev/zvol/dsk/rpool/VARSHARE/zones/kz01/disk0
>   0
>   bootpri: 0
> device:
>   match not specified
>   storage: dev:/dev/zvol/dsk/tank/device
>   2
>   bootpri: 2
> capped-memory:
>   physical: 2G
> keysource:
>   raw redacted
> zonecfg:kz01>
> 
> root@kz01:~# format
> Searching for disks...done
> 
> AVAILABLE DISK SELECTIONS:
> . c1d0
>   /kz-devices@ff/disk@0
>   c1d2
>   /kz-devices@ff/disk@2
> Specify disk (enter its number): ^C
> root@kz01:~# zpool create test1 c1d2
> root@kz01:~# zpool list
> NAMESIZE  ALLOC   FREE  CAP  DEDUP  HEALTH  ALTROOT
> rpool  15.9G  5.35G  10.5G  33%  1.00x  ONLINE  -
> test1  9.94G   124K  9.94G   0%  1.00x  ONLINE  -
> root@kz01:~#
> 
> Thinking little bit more, for we already can add zvol to kvm zone, it
> should not be very hard to realize in OS/LX zone.
> 
> Thanks.
> 
> Fred
> 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] add device to OS/LX zone

[Fred Liu]

Hi,

For I have no spare hardware(disk), I have tried adding zvol to OS/LX zone. But 
it looks likes not working as the document.
zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8:device> set 
match=/dev/zvol/rdsk/zones/device
zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8:device> end
zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8> verify
zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8> exit

[root@pluto /zones/build]# zlogin f58e8c87-eb04-ea48-bf23-9b7be32515b8
[Connected to zone 'f58e8c87-eb04-ea48-bf23-9b7be32515b8' pts/6]
Last login: Tue Feb 27 20:25:02 on pts/6
   __.   .
 _|  |_  | .-. .  . .-. :--. |-
|__| ;|   ||  |(.-' |  | |
  |__|   `--'  `-' `;-| `-' '  ' `-'
   /  ; Instance (base-multiarch-lts 15.4.0)
   `-'  https://docs.joyent.com/images/smartos/base

[root@f58e8c87-eb04-ea48-bf23-9b7be32515b8 ~]# ls -la 
/dev/zvol/rdsk/zones/device
crw--- 1 root sys 90, 26 Feb 27 20:35 /dev/zvol/rdsk/zones/device
[root@f58e8c87-eb04-ea48-bf23-9b7be32515b8 ~]# newfs /dev/zvol/rdsk/zones/device
newfs: construct a new file system /dev/zvol/rdsk/zones/device: (y/n)? y
can't check mount point; can't stat 


Will the real hardware be different?

I also tried adding zvol to zones on solaris11.2. It works well.
device:
match not specified
storage.template: 
dev:/dev/zvol/dsk/%{global-rootzpool}/VARSHARE/zones/%{zonename}/disk%{id}
storage: dev:/dev/zvol/dsk/rpool/VARSHARE/zones/kz01/disk0
id: 0
bootpri: 0
device:
match not specified
storage: dev:/dev/zvol/dsk/tank/device
id: 2
bootpri: 2
capped-memory:
physical: 2G
keysource:
raw redacted
zonecfg:kz01> 

root@kz01:~# format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
   0. c1d0 
  /kz-devices@ff/disk@0
   1. c1d2 
  /kz-devices@ff/disk@2
Specify disk (enter its number): ^C
root@kz01:~# zpool create test1 c1d2
root@kz01:~# zpool list
NAMESIZE  ALLOC   FREE  CAP  DEDUP  HEALTH  ALTROOT
rpool  15.9G  5.35G  10.5G  33%  1.00x  ONLINE  -
test1  9.94G   124K  9.94G   0%  1.00x  ONLINE  -
root@kz01:~#

Thinking little bit more, for we already can add zvol to kvm zone, it should 
not be very hard to realize in OS/LX zone.

Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[jira] [Commented] (NIFI-4845) Add JanusGraph put processor

[Fred Liu (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358015#comment-16358015
 ] 

Fred Liu commented on NIFI-4845:


Hi [~mcgilman], Can you assign this task to me? Is this new processor necessary?

> Add JanusGraph put processor
> 
>
> Key: NIFI-4845
> URL: https://issues.apache.org/jira/browse/NIFI-4845
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>    Reporter: Fred Liu
>Priority: Major
>
> Create processor for Reading records from an incoming FlowFile using the 
> provided Record Reader, and writting those records to JanusGraph. And using a 
> JanusGraphControllerService is good.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4845) Add JanusGraph put processor

[Fred Liu (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16353509#comment-16353509
 ] 

Fred Liu commented on NIFI-4845:


Hi Admin, Please assign this task to me so that I can begin working on the 
implementation.

> Add JanusGraph put processor
> 
>
> Key: NIFI-4845
> URL: https://issues.apache.org/jira/browse/NIFI-4845
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>    Reporter: Fred Liu
>Priority: Major
>
> Create processor for Reading records from an incoming FlowFile using the 
> provided Record Reader, and writting those records to JanusGraph. And using a 
> JanusGraphControllerService is good.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (NIFI-4845) Add JanusGraph put processor

[Fred Liu (JIRA)]

Fred Liu created NIFI-4845:
--

 Summary: Add JanusGraph put processor
 Key: NIFI-4845
 URL: https://issues.apache.org/jira/browse/NIFI-4845
 Project: Apache NiFi
  Issue Type: New Feature
  Components: Extensions
Reporter: Fred Liu


Create processor for Reading records from an incoming FlowFile using the 
provided Record Reader, and writting those records to JanusGraph. And using a 
JanusGraphControllerService is good.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (NIFI-4494) Add a FetchOracleRow processor

[Fred Liu (JIRA)]

Fred Liu created NIFI-4494:
--

 Summary: Add a FetchOracleRow processor
 Key: NIFI-4494
 URL: https://issues.apache.org/jira/browse/NIFI-4494
 Project: Apache NiFi
  Issue Type: New Feature
  Components: Extensions
 Environment: oracle
Reporter: Fred Liu


We encounter a lot of demand, poor data quality, no primary key, no time stamp, 
and even a lot of duplicate data. But the customer requires a high performance 
and accuracy.

Using GenerateTableFetch or QueryDatabaseTable, we can not meet the functional 
and performance requirements. So we want to add a new processor, it is 
specifically for the oracle database, able to ingest very poor quality data and 
have better performance.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

RE: [smartos-discuss] rotate-kvm-log

[Fred Liu]

> 
> Hi Fred,
> 
> That'll only be true if the KVM VM is never booted. Whenever it is booted, the
> file will be non-empty until it is rotated since there are always messages
> written to the log when a KVM VM boots.
> 

 All of my KVM VMs are definitely running now.  I think
It came from the 'copytruncate' by "logadm -c". Once rotate-kvm-logs.sh ends,
all the non-empty vm.log files are rotating into "/var/log/sdc/upload/qemu-xxx".
And if rotate-kvm-log.sh runs again, no new entry will be generated.

 
> 
> 
>   Plus, I also notice that there is logadm invocation during "vmadm 
> create"
> in lines from #625 to #641 of source
> (https://github.com/joyent/smartos-live/blob/64998c0b5a7c33287eb7dd118fef
> 4aea42e5a6f3/src/vm/sbin/vmadmd.js#L625
>  f4aea42e5a6f3/src/vm/sbin/vmadmd.js#L625> ) --
> 
> 
> 
> 
> You're right. I had forgotten about this code in vmadmd. I had looked only at
> vmadm.
> 
> I don't see how this changes anything though. Because it's still the
> rotate-kvm-logs.sh that it's calling to do the rotation. The same thing would
> have happened at the first cron execution after this if vmadmd didn't do it.
> 
> Since it seems that fixing the bug in logadm that causes this problem might be
> a while still in coming, I will look into the prospect of adding a workaround 
> that
> runs:
> 
> logadm -r /zones//root/tmp/vm.log
> 
> when deleting a KVM VM, or in the rotate-kvm-logs.sh itself when it sees a VM
> no longer exists. I've filed https://smartos.org/bugview/OS-6053 to look into
> this.

From my side, the intuitive and direct way is removing the entry by "vmadm 
destroy".
We can also add the similar cose in vmadmd source.


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] rotate-kvm-log

[Fred Liu]

>From: Josh Wilsdon [mailto:jwils...@joyent.com] 
>Sent: 星期三, 四月 12, 2017 0:25
>To: smartos-discuss@lists.smartos.org
>Subject: Re: [smartos-discuss] rotate-kvm-log


>Yes. But "/usr/vm/sbin/rotate-kvm-logs.sh script" won't add entries in 
>"/var/logadm/timestamps" like following:
 
>"/zones/c3f09892-f36e-4784-9853-b4ceb3e762da/root/tmp/vm.log -P 'Wed Jan  4 
>05:20:15 2017'"

>The weirdness is how this type of entry has been added per every kvm instance?

>Fred,

>That's exactly what the entries look like that come from running 
>rotate-kvm-logs.sh. What evidence do you have that it's not that script? When 
>I manually ran rotate-kvm-logs.sh without any cron involved, it just generated 
>an entry:

>/zones/3d93a436-3a86-4406-ae69-fbaaf67b45b7/root/tmp/vm.log -P 'Tue Apr 11 
>16:20:40 2017'

Josh,

I think I see exactly the same issue 
(https://github.com/joyent/smartos-live/issues/319).
The reason why I haven't got the concerning entry is lines from  #36 to #38 of 
the source 
(https://github.com/joyent/smartos-live/blob/64998c0b5a7c33287eb7dd118fef4aea42e5a6f3/src/vm/sbin/rotate-kvm-logs.sh#L36)
 -- 

"
 if [[ ! -s ${logfile} ]]; then
# file doesn't exist or is empty
return;
fi
".

Because all my ${logfile} has size of 0,   rotate_log() returns.
And the script won't go to lines from #72 to 
#78(https://github.com/joyent/smartos-live/blob/64998c0b5a7c33287eb7dd118fef4aea42e5a6f3/src/vm/sbin/rotate-kvm-logs.sh#L72)
 -- 

"
logadm \
-c \
-s 1b \
-p now \
-t '$dirname/vm.log.rotating' \
-R "cat \$file >> ${destfile} && rm -f \$file" \
${logfile}
"

Plus, I also notice that there is logadm invocation during "vmadm create" in 
lines from #625 to #641 of source 
(https://github.com/joyent/smartos-live/blob/64998c0b5a7c33287eb7dd118fef4aea42e5a6f3/src/vm/sbin/vmadmd.js#L625)
 --

"
unction rotateKVMLog(vm_uuid)
{
setTimeout(function () {
execFile('/usr/vm/sbin/rotate-kvm-logs.sh', [vm_uuid],
function (error, stdout, stderr) {
if (error) {
log.error({err: error, stdout: stdout, stderr: stderr},
'failed to rotate kvm log for just-booted ' + vm_uuid);
return;
}
log.debug({stdout: stdout, stderr: stderr}, 'rotated kvm log '
+ 'for just-booted ' + vm_uuid);
return;
}
);
}, 30 * 1000);
}

"

Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] rotate-kvm-log

[Fred Liu]

>From: Josh Wilsdon [mailto:jwils...@joyent.com] 
>It doesn't go in logadm.conf. The rotation happens via the 
>/usr/vm/sbin/rotate-kvm-logs.sh script which is run by root's crontab in the 
>GZ.

Yes. But "/usr/vm/sbin/rotate-kvm-logs.sh script" won't add entries in 
"/var/logadm/timestamps" like following:

"/zones/c3f09892-f36e-4784-9853-b4ceb3e762da/root/tmp/vm.log -P 'Wed Jan  4 
05:20:15 2017'"

The weirdness is how this type of entry has been added per every kvm instance?


Thanks.

Fred





---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] rotate-kvm-log

[Fred Liu]

But there is  nothing about rotate-kvm-log in /etc/logadm.conf from stock. It 
is weird. How were these entries had been added in time stamp? It should be 
logadm command invoking. But where was it invoked? I haven't done it manually.


Fred

Get Outlook for iOS



On Tue, Apr 11, 2017 at 3:52 AM +0800, "Josh Wilsdon" 
> wrote:


I am running joyent_20161013T025521Z now. It seems in this version 
rotate-kvm-log is done by cron not logadm.
But I also noticed when a kvm instance was created there was a corresponding 
entry occurred in /var/logadm/timestamp like following:
"/zones/c3f09892-f36e-4784-9853-b4ceb3e762da/root/tmp/vm.log -P 'Wed Jan  4 
05:20:15 2017'". Is this from the "vmadm create" operation?

And it looks because of this bug(https://smartos.org/bugview/OS-3097), if the 
kvm instance is destroyed, the corresponding logadm action won't be removed.


Hi Fred,

Using "vmadm create" does not do anything with log rotation, neither does 
"vmadm delete", but what you're seeing there does look like what ends up 
happening due to this logadm bug.

Thanks,
Josh
smartos-discuss | Archives 
[https://www.listbox.com/images/feed-icon-10x10.jpg96494be.jpg?uri=aHR0cHM6Ly93d3cubGlzdGJveC5jb20vaW1hZ2VzL2ZlZWQtaWNvbi0xMHgxMC5qcGc]
   | 
Modify Your Subscription   
[https://www.listbox.com/images/listbox-logo-small.png96494be.png?uri=aHR0cHM6Ly93d3cubGlzdGJveC5jb20vaW1hZ2VzL2xpc3Rib3gtbG9nby1zbWFsbC5wbmc]
 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] rotate-kvm-log

[Fred Liu]

Hi,

I am running joyent_20161013T025521Z now. It seems in this version 
rotate-kvm-log is done by cron not logadm.
But I also noticed when a kvm instance was created there was a corresponding 
entry occurred in /var/logadm/timestamp like following:
"/zones/c3f09892-f36e-4784-9853-b4ceb3e762da/root/tmp/vm.log -P 'Wed Jan  4 
05:20:15 2017'". Is this from the "vmadm create" operation?

And it looks because of this bug(https://smartos.org/bugview/OS-3097), if the 
kvm instance is destroyed, the corresponding logadm action won't be removed.

Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] vnic mac address updatable?

[Fred Liu]

> -Original Message-
> From: Johan Claesson [mailto:jo...@jobetech.se]
> Sent: 星期四, 一月 05, 2017 20:01
> To: smartos-discuss@lists.smartos.org
> Subject: Re: [smartos-discuss] vnic mac address updatable?
> 
> 2017-01-05 04:32 skrev Fred Liu:
> > Hi,
> >
> >
> > Sorry, if there is already answer. From crossbow heritage, this
> > property should be configurable just like what I am doing in LDOM of
> > Solaris.
> > What is the reason why it is not applicable in smartos? The main
> > purpose here is to migrate legacy hardware.
> >
> 
> The MAC of a VNIC can only be set during creation.
> So, you first need to remove it and then re-add it with the "mac"
> property set to you desired value.
> If you don't set the "mac" property it will be auto-generated for you.
> 
> 

It works exactly as what you described.


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [SCIENTIFIC-LINUX-USERS] is the sha256sum of SL-7.3-x86_64-netinst.iso correct?

[Fred Liu]

G

> -Original Message-
> From: Pat Riehecky [mailto:riehe...@fnal.gov]
> Sent: 星期一, 四月 03, 2017 22:20
> To: Fred Liu; scientific-linux-us...@listserv.fnal.gov
> Subject: Re: [SCIENTIFIC-LINUX-USERS] is the sha256sum of
> SL-7.3-x86_64-netinst.iso correct?
> 
> Good catch.  Somehow the signature got reverted to the RC image.
> 
> The correct signature is
> 68992289a1163250ba064c23baa8c4b23d11e5dc0562de41971bdf9c2ad42415
> 
> I'll get a new set of SHA files posted.  Sorry for the error.
> 
> On 04/01/2017 03:06 AM, Fred Liu wrote:
> > Hi,
> >
> > Is the following hash the correct one?
> >
> > 13650ef94c16024285fd9dadebba4d62a33c0de5ac611314bf8e3d6afb956a3a
> SL-7.3-x86_64-netinst.iso
> >
> >
> > Thanks.
> >
> > Fred

is the sha256sum of SL-7.3-x86_64-netinst.iso correct?

[Fred Liu]

Hi,

Is the following hash the correct one?

13650ef94c16024285fd9dadebba4d62a33c0de5ac611314bf8e3d6afb956a3a  
SL-7.3-x86_64-netinst.iso


Thanks.

Fred

[jira] [Created] (AIRFLOW-1031) 'scheduled__' may replace with DagRun.ID_PREFIX in DagRun.run_id

[Fred Liu (JIRA)]

Fred Liu created AIRFLOW-1031:
-

 Summary: 'scheduled__' may replace with DagRun.ID_PREFIX in 
DagRun.run_id
 Key: AIRFLOW-1031
 URL: https://issues.apache.org/jira/browse/AIRFLOW-1031
 Project: Apache Airflow
  Issue Type: Improvement
  Components: DagRun
Affects Versions: Airflow 1.8
Reporter: Fred Liu
Assignee: Fred Liu
Priority: Trivial
 Fix For: Airflow 1.8


https://github.com/apache/incubator-airflow/blob/v1-8-stable/airflow/jobs.py#L840

This 'scheduled__' may replace with DagRun.ID_PREFIX
I searched 'scheduled__', it seems don't appear other code.
Can I send a PR to fix this?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [OpenIndiana-discuss] The end is near

[Fred Liu]

> -Original Message-
> From: Jonathan Adams [mailto:t12nsloo...@gmail.com]
> Sent: 星期五, 一月 20, 2017 18:23
> To: Discussion list for OpenIndiana
> Subject: Re: [OpenIndiana-discuss] The end is near
> 
> On 20 January 2017 at 02:14, Alex Smith (K4RNT) 
> wrote:
> 
> > http://shop.lenovo.com/us/en/systems/storage/sds/nexentastor/
> >
> > ...
> 
> >
> > " 'With the first link, the chain is forged. The first speech
> > censured, the first thought forbidden, the first freedom denied,
> > chains us all irrevocably.' Those words were uttered by Judge Aaron
> > Satie as wisdom and warning... The first time any man's freedom is
> > trodden on, we’re all damaged." - Jean-Luc Picard, quoting Judge Aaron
> > Satie, Star Trek: TNG episode "The Drumhead"
> > - Alex Smith
> > - Kent, Washington (metropolitan Seattle area)
> >
> >
> You only gave one link, so it must be the first ... and with the guarded 
> comment
> you've made I'm not going to click on it ... 
> ___

Nexenta has to co-work with hardware OEMs for nexentastor is just software. As 
long as I know, they rolled out they-called software-defined storage appliances 
with Dell, PogoLinux, Supermicro etc. I even installed nexentasor on generic 
x86 hardware(I forgot the detailed configurations..).


Fred
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] The end is near

[Fred Liu]

> -Original Message-
> From: Alan Coopersmith [mailto:alan.coopersm...@oracle.com]
> Sent: 星期五, 一月 20, 2017 8:44
> To: Discussion list for OpenIndiana; Apostolos Syropoulos
> Subject: Re: [OpenIndiana-discuss] The end is near
> 
> On 01/19/17 12:38 AM, Fred Liu wrote:
> > From that roadmap, my understanding is there is no on-premise and
> standalone Solaris and SPARC releases after 2017 and everything goes into
> cloud.
> 
> Then you're misunderstanding the roadmap, which shows both on-premise &
> cloud
> releases going forward until at least 2021.
> 
> > So data-machine and fishwork-storage are some kinds of variations from
> Solaris and SPARC, if users want to touch by hand.
> 
> ZFS Storage Appliances ("fishworks") use x86 CPUs and their own OS versions,
> with their own release schedules.   You can't make any assumptions about
> them based on the roadmap for CPU's they don't use or OS versions they don't
> use.
> 

OK. See. I might be impressed by the recent fud about RIF of Solaris/SPARC 
team. Anyway SPARC on cloud is good try but definitely has impact on 
on-premises implementation from my point of view. Nobody wants to see the 
demise of SPARC. Let's see how it goes.


Thanks.

Fred
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] The end is near

[Fred Liu]

> -Original Message-
> From: Alan Coopersmith [mailto:alan.coopersm...@oracle.com]
> Sent: 星期四, 一月 19, 2017 13:25
> To: Discussion list for OpenIndiana; Apostolos Syropoulos
> Subject: Re: [OpenIndiana-discuss] The end is near
> 
> On 01/18/17 08:58 PM, Fred Liu wrote:
> > Will they still sell data machine, fishwork storage?
> 
> Yes - those systems have their own roadmap, separate from the SPARC &
> Solaris roadmap.  (But we're really getting off-topic here for the OpenIndiana
> mailing list.)
> 

From that roadmap, my understanding is there is no on-premise and standalone 
Solaris and SPARC releases after 2017 and everything goes into cloud. If there 
are such needs, users have to buy cloud services from Oracle. Is it correct? So 
data-machine and fishwork-storage are some kinds of variations from Solaris and 
SPARC, if users want to touch by hand.


Thanks.

Fred
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] The end is near

[Fred Liu]

Will they still sell data machine, fishwork storage?

> -Original Message-
> From: Apostolos Syropoulos via openindiana-discuss
> [mailto:openindiana-discuss@openindiana.org]
> Sent: 星期四, 一月 19, 2017 3:53
> To: Discussion List for OpenIndiana
> Subject: [OpenIndiana-discuss] The end is near
> 
> 
> 
> http://www.oracle.com/us/products/servers-storage/servers/sparc/oracle-spa
> rc/sparc-roadmap-slide-2076743.pdf
>  --
> Apostolos Syropoulos
> Xanthi, Greece
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[smartos-discuss] vnic mac address updatable?

[Fred Liu]

Hi,


Sorry, if there is already answer. From crossbow heritage, this property should 
be configurable just like what I am doing in LDOM of Solaris.
What is the reason why it is not applicable in smartos? The main purpose here 
is to migrate legacy hardware.



Thanks.



Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] vnc resolution configurable?

[Fred Liu]

Hi,

We noticed that GUI since SL7.2 did not work with the low resolution 1024x768 
which is the default-detected resolution from SmartOS vnc server.
Is there a way to configure the vnc to run in higher resolution like 1280x1024? 
And I don't need to hack Linux to forcedly run in higher resolution.

BTW, is spice stable enough on SmartOS?


Thanks.

Fred
> -Original Message-
> From: Nahum Shalman [mailto:nshalman-smar...@elys.com]
> Sent: 星期一, 三月 25, 2013 21:01
> To: smartos-discuss@lists.smartos.org
> Cc: Alain O'Dea
> Subject: Re: [smartos-discuss] Cannot get working VNC Viewer onto KVM Zone
> 
> On 03/23/2013 09:56 PM, Alain O'Dea wrote:
> > Is SPICE a feasible option here?  I notice the experimental
> > configuration options for it.  I'm really only looking at having a
> > console long enough to install the OS and bootstrap a Bomgar session
> > onto the desktop.
> 
> Feasible, possibly. Ideal, probably not.
> In order to use Spice, you need to use an alternate QEMU binary rather than
> the one that ships with the platform.
> (See http://wiki.smartos.org/display/DOC/Spice+on+SmartOS for details)
> 
> The benefit of using "my" QEMU is that you can use Spice. The biggest down
> side is that if you run into problems, you're not using the Joyent supported
> QEMU.
> 
> One option if you're trying to build a fresh image to use later as a template 
> that
> will have SSH already working, you could try using the Spice enabled QEMU for
> the stage of building your image, verify that a fresh boot of that image does
> bring up SSH as desired, then use that image with the platform QEMU.
> 
> So, order of preference from best to worst from my perspective:
>Try to get VNC working.
>Use Spice enabled QEMU for image building, platform QEMU for production
> workload.
>Use Spice enabled QEMU for building and running in production
> 
> I do run "my" QEMU in production, but I can't provide support.
> 
> -Nahum
> 
> P.S.  I might not-so-secretly be hoping that you'll choose #3 *and* that 
> you'll
> then ask Joyent to support it... A guy can dream.
> 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [OmniOS-discuss] any supoorted in Mellanox HBA in illumos?

[Fred Liu]

This is encouraging!

Thanks.

Fred

> -Original Message-
> From: wo...@4amlunch.net [mailto:wo...@4amlunch.net]
> Sent: 星期三, 十一月 30, 2016 20:04
> To: Fred Liu
> Cc: omnios-discuss@lists.omniti.com; smartos-disc...@lists.smartos.org;
> Discussion list for OpenIndiana; develo...@lists.illumos.org
> Subject: Re: [OmniOS-discuss] any supoorted in Mellanox HBA in illumos?
> 
> I'm using ConnectX-2 cards in my OmniOS fileserver. Everything works 
> perfectly.
> Including SRP (SCSI RDMA). I use it with ESXi hosts.
> 
> -brian
> 
> > On Nov 30, 2016, at 06:47, Fred Liu <fred_...@issi.com> wrote:
> >
> > Hi,
> >
> > Please post if you know.
> >
> >
> > Thanks.
> >
> > Fred
> > ___
> > OmniOS-discuss mailing list
> > OmniOS-discuss@lists.omniti.com
> > http://lists.omniti.com/mailman/listinfo/omnios-discuss
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OpenIndiana-discuss] [OmniOS-discuss] any supoorted in Mellanox HBA in illumos?

[Fred Liu]

This is encouraging!

Thanks.

Fred

> -Original Message-
> From: wo...@4amlunch.net [mailto:wo...@4amlunch.net]
> Sent: 星期三, 十一月 30, 2016 20:04
> To: Fred Liu
> Cc: omnios-disc...@lists.omniti.com; smartos-disc...@lists.smartos.org;
> Discussion list for OpenIndiana; develo...@lists.illumos.org
> Subject: Re: [OmniOS-discuss] any supoorted in Mellanox HBA in illumos?
> 
> I'm using ConnectX-2 cards in my OmniOS fileserver. Everything works 
> perfectly.
> Including SRP (SCSI RDMA). I use it with ESXi hosts.
> 
> -brian
> 
> > On Nov 30, 2016, at 06:47, Fred Liu <fred_...@issi.com> wrote:
> >
> > Hi,
> >
> > Please post if you know.
> >
> >
> > Thanks.
> >
> > Fred
> > ___
> > OmniOS-discuss mailing list
> > omnios-disc...@lists.omniti.com
> > http://lists.omniti.com/mailman/listinfo/omnios-discuss
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[smartos-discuss] RE: [OmniOS-discuss] any supoorted in Mellanox HBA in illumos?

[Fred Liu]

This is encouraging!

Thanks.

Fred

> -Original Message-
> From: wo...@4amlunch.net [mailto:wo...@4amlunch.net]
> Sent: 星期三, 十一月 30, 2016 20:04
> To: Fred Liu
> Cc: omnios-disc...@lists.omniti.com; smartos-discuss@lists.smartos.org;
> Discussion list for OpenIndiana; develo...@lists.illumos.org
> Subject: Re: [OmniOS-discuss] any supoorted in Mellanox HBA in illumos?
> 
> I'm using ConnectX-2 cards in my OmniOS fileserver. Everything works 
> perfectly.
> Including SRP (SCSI RDMA). I use it with ESXi hosts.
> 
> -brian
> 
> > On Nov 30, 2016, at 06:47, Fred Liu <fred_...@issi.com> wrote:
> >
> > Hi,
> >
> > Please post if you know.
> >
> >
> > Thanks.
> >
> > Fred
> > ___
> > OmniOS-discuss mailing list
> > omnios-disc...@lists.omniti.com
> > http://lists.omniti.com/mailman/listinfo/omnios-discuss


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[OmniOS-discuss] any supoorted in Mellanox HBA in illumos?

[Fred Liu]

Hi,

Please post if you know.


Thanks.

Fred
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

[smartos-discuss] any supoorted in Mellanox HBA in illumos?

[Fred Liu]

Hi,

Please post if you know.


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] SmartOS release-20161013

[Fred Liu]

> -Original Message-
> From: Trent Mick [mailto:trent.m...@joyent.com]
> Sent: 星期五, 十月 14, 2016 5:35
> To: smartos-discuss@lists.smartos.org
> Subject: [smartos-discuss] SmartOS release-20161013
> 
> Hello All,
> 
> The latest bi-weekly "release" branch build of SmartOS is up:
> 
> curl -C - -O
> https://us-east.manta.joyent.com/Joyent_Dev/public/SmartOS/smartos-latest
> .iso
> curl -C - -O
> https://us-east.manta.joyent.com/Joyent_Dev/public/SmartOS/smartos-latest
> -USB.img.bz2
> curl -C - -O
> https://us-east.manta.joyent.com/Joyent_Dev/public/SmartOS/smartos-latest.
> vmwarevm.tar.bz2
> 
> A generated changelog is here:
> 
> 
> https://us-east.manta.joyent.com/Joyent_Dev/public/SmartOS/smartos.html#
> 20161013T025521Z
> 
> The full build bits directory, for those interested, is here in Manta:
> 
> /Joyent_Dev/public/SmartOS/20161013T025521Z
> 
> 
> # Highlights
> 
> - NVMe 1.1 support
> - GNU screen has been updated to 4.4.0-32, and now includes support for
> vertical
>   splits.
> 
> 
We are running this release for several days. Works like charm!
1): NVMe 1.1 is so sweet.
2): USB device is recognized again.
3): KVM improvement -- ext4 corruption warning disappears in SL6.7.

Tremendous thanks for your awesome work!!


Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] enable services in smartos

[Fred Liu]

> -Original Message-
> From: Jonathan Perkin [mailto:jper...@joyent.com]
> Sent: 星期二, 十月 18, 2016 17:33
> To: smartos-discuss@lists.smartos.org
> Subject: Re: [smartos-discuss] enable services in smartos
> 
> * On 2016-10-18 at 10:19 BST, Fred Liu wrote:
> 
> > It looks nis/client has been added as a dependency in 20160901 but
> > not in 20160527 like following;
> 
> Correct, this was to fix https://smartos.org/bugview/OS-5568
> 
> > I totally understand minimalism, but some disabled services we
> > really need such ldap, dns and nis etc.
> >
> > What is the simplest way to enable these services?
> 
> I would use jclulow's rc.local gist:
> 
>   https://gist.github.com/jclulow/2606370
> 
> and then just add the svcadm commands to the postboot script.
> 

Good idea as a command hub!


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] enable services in smartos

[Fred Liu]

Hi

It looks nis/client has been added as a dependency in 20160901 but not in 
20160527 like following;

uname -a
SunOS pluto 5.11 joyent_20160901T054050Z i86pc i386 i86pc
svcs -l name-services
fmri svc:/milestone/name-services:default
name name services milestone
enabled  true
stateonline
next_state   none
state_time   October 18, 2016 01:40:50 PM CST
alt_logfile  /etc/svc/volatile/milestone-name-services:default.log
logfile  /var/svc/log/milestone-name-services:default.log
restartersvc:/system/svc/restarter:default
dependency   optional_all/refresh svc:/network/dns/client (disabled)
dependency   optional_all/refresh svc:/network/ldap/client (disabled)
dependency   optional_all/refresh svc:/network/nis/client (disabled)


uname -a
SunOS kepler-452b 5.11 joyent_20160527T033529Z i86pc i386 i86pc

svcs -l name-services
fmri svc:/milestone/name-services:default
name name services milestone
enabled  true
stateonline
next_state   none
state_time   October 18, 2016 05:05:38 PM CST
alt_logfile  /etc/svc/volatile/milestone-name-services:default.log
logfile  /var/svc/log/milestone-name-services:default.log
restartersvc:/system/svc/restarter:default
dependency   optional_all/refresh svc:/network/dns/client (disabled)
dependency   optional_all/refresh svc:/network/ldap/client (disabled)
dependency   optional_all/refresh svc:/network/nis/client (absent)

I totally understand minimalism, but some disabled services we really need such 
ldap, dns and nis etc.

What is the simplest way to enable these services?
I have tried add my own services under /opt but it can't be a dependency for 
other services because of hard-coded name space.
I also think about enabling them when build smartos. Is there anyone who knows 
how to do it when I am building smartos?
Building normally takes some time. And it should not be a best way.
Brainstorm.


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] Samsung 950 Pro on SmartOS?

[Fred Liu]

> -Original Message-
> From: Fred Liu
> Sent: 星期三, 三月 09, 2016 13:02
> To: smartos-discuss@lists.smartos.org
> Cc: illumos-developer
> Subject: RE: [smartos-discuss] Samsung 950 Pro on SmartOS?
> 
> 
> 
> From: Dirk Steinberg [mailto:d...@steinbergnet.net]
> Sent: 星期三, 三月 09, 2016 0:06
> To: smartos-discuss@lists.smartos.org
> Subject: Re: [smartos-discuss] Samsung 950 Pro on SmartOS?
> 
> 
> Am 07.03.2016 um 06:48 schrieb Fred Liu <fred.f...@gmail.com>:
> 
> 
> 2016-03-05 21:19 GMT+08:00 Dirk Steinberg <d...@steinbergnet.net>:
> > Apart from that: is NVMe support in SmartOS considered stable?
> 
> 
> There is driver support for it in the system. I have not heard many
> reports positively or negatively about it.
> 
> [Fred]: I am testing some Intel P3600 NVMe SSD. In normal workload, they just
> work . But in burning mode like continuous scrubbings, I have got lots of
> checksum errors. And I tested the same scrubbings under Linux, no checksum
> errors were found.
> Fred
> 
> Hi Fred,
> 
> do you attribute these errors to the SmartOS NVMe driver?
> Sounds like it since you are saying that the same SSD works under Linux.
> 
> So have you given up on NVMe on SmartOS?
> 
> [Fred]: I personally attribute those errors to the immaturity of the NVMe 
> driver
> in Illumos. But that  is not so severe based on the fact that there are no
> substantial data loss with those checksum errors.
> I used to get some some kernel panics under "too may check sum erros" and
> after disabling "sha512|skeun|edonr" checksum algorithm, the server has
> been running well for more than two weeks.
> It looks like "sha512|skeun|edonr" checksum algorithm still has some glitches.
> 
> Thanks.
>

[Fred]: With the patch 7321 (https://www.illumos.org/issues/7312), I can 
confirm these checksum errors are all gone.


Thanks.

Fred 
> 
> Sorry, I am not quite sure what you are trying to tell me.
> 
> I am running the sha512 hash on a regular disk pool without problems. I have
> also
> run a number of scrubs. I assume the the sha512 hash is working correctly.
> If I had a ton of checksum errors from ZFS I would be VERY concerned.
> Just turning off the checksum may not be the solution…
> I do not think that a bug in sha512 is generating these.
> 
> Also, what do you mean by „no substantial data loss“? Either there is
> data loss or there is no data loss. My policy here is that even a single
> bit of data loss is not acceptable. This is why ZFS goes to all the
> effort of using strong checksums and redundancy and scrubbing and so on…
> 
> If you are willing to accept „some nonsubstantial data loss“ and turn
> of checksums so as not to be bothered by all these checksum errors
> there is not much point in using ZFS in the first place!
> 
> Am I understanding something incorrectly?
> 
> [Fred]: "NVMe support" and "[sha512|skein|edonr] hash algorithm" are the
> major spot-lights
>  of Illumos in 2015. I am running 20160218T022556Z now. Disabling
> "sha512|skein|edonr"
>  doesn't mean setting "checksum=off". In default("checksum=on"),
> zfs automatically
>  selects an appropriate algorithm if these
> features("[sha512|skein|edonr]") are enabled.
>  I met random server reboots(triggered by zfs deadman) and panics.
> But I could not get
>  the nitty-gritty reason from core dump. And we do have very stable
> running of release of
>  2014. To reason by exclusive method, I recreated the zpool and set
> "checksum=sha256". And
>  till now the server has been running well at least for two weeks.
> This operation does
>  not intend to remove the *annoying* checksum errors.
>  As for "no substantial data loss", that means "zpool status" always
> show "errors: No known data errors" even with "too many checksum errors".
> 
> Thanks.
> 
> Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [Beowulf] NFS HPC survey results.

[Fred Liu]

Very informative!

Thank you so much!


Fred

> -Original Message-
> From: Beowulf [mailto:beowulf-boun...@beowulf.org] On Behalf Of Bill
> Broadley
> Sent: 星期四, 七月 21, 2016 7:19
> To: Beowulf@beowulf.org
> Subject: [Beowulf] NFS HPC survey results.
> 
> 
> Many thanks for all the responses.
> 
> Here's the promised raw data:
> https://wiki.cse.ucdavis.edu/_media/wiki:linux-hpc-nfs-survey.csv
> 
> I'll summarize the 26 results below.  I'll email similar to those that asked.
> 
> Not everyone answered all questions.
> 
> 1) cluster OS:
>72% Redhat/CentOS/Scientific linux or derivative
>24% Debian/Ubuntu or derivative
> 4% SUSE or derivative
> 
> 2) Appliance/NAS or linux server
> 32% NFS appliance
> 76% linux server
> 12% other (illumos/Solaris)
> 
> 3) Appliances used (one each, free form answers):
> * Hitachi BlueARC, EMC Isilon, DDN/GPFS, x4540
> * Not sure - something that corporate provided. An F5, maybe...? Also a
> Panasas system for /scratch.
> * NetApp FAS6xxx
> * netapp
> * isilon x and nl
> * Isilon
> * NetApp
> * Synology
> 
> 4) Which kernel do you use:
> 88% one provided with the linux distribution
> 12% one that I compile/tweak myself
> 
> 5) what kernel changes do you make
> * CPU performance tweaking, network performance.
> * raise ARP cache size, newer kernel than stock 3.2 was needed for newer
>   hardware 3.14 at the moment
> * ZFS
> 
> 6) Do you often see problems like nfs: server 192.168.5.30 not responding,
> timed out:
> 42.3% Never
> 23.1% Sometimes
> 19.2% rarely
>  7.7% daily
>  7.7% often
> 
> 7) If you see NFS time outs what do you do (free form answers)
>* nothing
>* nothing
>* Restart NFSd, look for performance intensive jobs, sometimes increase
> NFSd.
>* Look at what's going on on that server. That means looking at what the
>  disks are doing, what network flows are going to/from that server and
>  determine if the load is something to take action on or to let.
>* Not much
>* Reboot
>* Resolve connectivity issue if any and run mount command on nodes. If this
>  doesn't fix it, then reboot.
>* Ignore them, unless they become a problem.
>* Look for the root cause of the issue, typically system is suffering 
> network
>  issues or is overloaded by a user 'abuse/missuse'.
>* diagnose and identify underlying cause
>* Try to figure out who is overloading the NFS server (hard job)
>* Troubleshoot, typically a machine is offline or network saturation
> 
> 8) which NFS options do you use (free form):
>* tcp,async,nodev,nosuid,rsize=32768,wsize=32768,timeout=10
>* nfsvers=3,nolock,hard,intr,timeo=16,retrans=8
>* hard,intr,rsize=32768,wsize=32768
>* all default
>* async
>* async,nodev,nosuid,rsize=32768,wsize=32768
>* tcp,async, nodev, nosuid,timeout=10
>* -rw,intr,nosuid,proto=tcp (mostly. Could be "ro" and/or "suid")
>*
> rsize=32768,wsize=32768,hard,intr,vers=3,proto=tcp,retrans=2,timeo=600
>* rsize=32768,wsize=32768
>* -nobrowse,intr,rsize=32768,wsize=32768,vers=3
>* udp,hard,timeo=50,retrans=7,intr,bg,rsize=8192,wsize=8192,nfsvers=3,
>  mountvers=3
>* RHEL defaults
>* default ones, they're almost always the best ones
>* rw,nosuid,nodev,tcp,hard,intr,vers=4
>*
> rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=t
> cp,
>  port=0,timeo=600,retrans=2,sec=sys,
> clientaddr=10.5.6.7,local_lock=none,
>  addr=10.5.6.1
>* defaults, netdev,vers=3
>* nfsvers=3,tcp,rw,hard,intr,timeo=600,retrans=2
>* rw,hard,tcp,nfsvers=3,noacl,nolock
>* default rhel6 (+nosuid, nodev, and sometimes nfsver=3)
>* tcp, intr, noauto, timeout, rsize, wsize, auto
>* nfsvers=3,rsize=1024,wsize=1024,cto
> 
> 9) Any explanations:
>* We have not yet made the change to nfsv4, we use nolock due to various
>  application "issues", we do not hard set rsize/wsize as they have been
>  negotiating better values for a number of years on their own under v3,
>  and the timeout/retrans are a bit of a legacy set of values from working
> on
>  this issue of server overload. Hard was a choice on our end to pick that
>  having things hang definitely seemed better then having things fail and
> go
>  stale. We still agree with the choice of hard. Intr just helps to
>  "interupt" stuck things when needed.
>* We like to be able to ctrl-C hung processes. For some systems we use
> larger
>  rsize/wsize if the vendor supports it.
>* works for me without tewaks
>* We didn't use tcp until the last couple of years.
>* Probably needs a revisit- block size was set up for 2.x series kernels
>* default of centos 7
>* nfsv4 was not stable enough last time out, don't fix rsize/wsize as
>  client/server usually negotiate to 1M anyway
>* We have frequent power outage (5+ times a 

Re: [OpenIndiana-discuss] [oi-dev] OpenIndiana user survey

[Fred Liu]

Done and thanks!

Fred
From: Adam Števko [mailto:adam.ste...@gmail.com]
Sent: 星期二, 七月 12, 2016 4:04
To: Discussion list for OpenIndiana; OpenIndiana Developer mailing list
Subject: [oi-dev] OpenIndiana user survey

Hi,

On behalf of the OI developers, I’d like to ask all the community members and 
developers to complete a short OpenIndiana survey form located at 
https://docs.google.com/forms/d/1k2LNzxQxGdUZ7joL_tI3Aid_fzTGPxSDEAp83PbCmus/viewform.

This will give us answers to several questions and the information will help us 
improve OpenIndiana.

Completing this form should not take more than 15 minutes and will help us 
tremendously, so I’d like to encourage all people on both lists to participate.

I’ll leave the form open till the end of August  2016.

Thanks for all answers!

Cheers,
Adam

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [oi-dev] OpenIndiana user survey

[Fred Liu]

Done and thanks!

Fred
From: Adam Števko [mailto:adam.ste...@gmail.com]
Sent: 星期二, 七月 12, 2016 4:04
To: Discussion list for OpenIndiana; OpenIndiana Developer mailing list
Subject: [oi-dev] OpenIndiana user survey

Hi,

On behalf of the OI developers, I’d like to ask all the community members and 
developers to complete a short OpenIndiana survey form located at 
https://docs.google.com/forms/d/1k2LNzxQxGdUZ7joL_tI3Aid_fzTGPxSDEAp83PbCmus/viewform.

This will give us answers to several questions and the information will help us 
improve OpenIndiana.

Completing this form should not take more than 15 minutes and will help us 
tremendously, so I’d like to encourage all people on both lists to participate.

I’ll leave the form open till the end of August  2016.

Thanks for all answers!

Cheers,
Adam

___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Re: [OmniOS-discuss] GRUB after omni install

[Fred Liu]

you may try reinstalling grub by "grubinstall"

Fred

Get Outlook for iOS

_
From: Josh Barton >
Sent: 星期五, 六月 3, 2016 7:47 上午
Subject: [OmniOS-discuss] GRUB after omni install
To: >


After installing omnios on a brand new supermicro machine and rebooting all I 
get isGRUB _ with no ability to type or do anything. Any thoughts on how to fix 
this and what might have caused it? Thanks!

Josh Barton
USU Research Foundation


After installing omnios on a brand new supermicro machine and rebooting all I 
get is GRUB _ with no ability to type or do anything. Any thoughts on how to 
fix this and what might have caused it? Thanks!

Josh Barton
USU Research Foundation
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

[smartos-discuss] Any possibilities in python OSError?

[Fred Liu]

Hi,

We are running some python scripts in LX brand ((CentOS 6.7 20151005).
And we get following errors:

File "/tool/iqs/bin/execd.py", line 416, in polljob
runfiles = [int(f) for f in os.listdir(RUNDIR) if f.isdigit()]
exceptions.OSError: [Errno 4] Interrupted system call: '/tool/iqs/run'



They have been running well under normal Linux OS.

Any possibilities?


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] test

[Fred Liu]

---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] Re: Any possibilities in python OSError?

[Fred Liu]

> -Original Message-
> From: Richard Elling [mailto:richard.ell...@richardelling.com]
> Sent: 星期一, 五月 16, 2016 21:45
> To: smartos-discuss@lists.smartos.org
> Subject: Re: [smartos-discuss] Re: Any possibilities in python OSError?
> 
> 
> > On May 16, 2016, at 3:40 AM, Fred Liu <fred.f...@gmail.com> wrote:
> >
> > It could be the slow read from the nfs path -- "/tool/iqs/run".
> > We see nfs v4 client not working in LX brand(I have already opened OS-5265).
> > And nfs v3 client is working but it has obvious lag( about 5-10
> > seconds) at the very first try to mount nfs path.
> > As long as the mount is done, there is no obvious lag in coming
> > nfs-related operations.
> > And further, we find if SmartOS where LX brands are living in serve
> > nfs service, the lag won't appear.
> > It could be something happened in network path.
> 
> this is consistent with name lookup timeout. double check dns, ldap, and all
> other name sources.
> 

I checked /etc/nsswitch.conf and I get following:
hosts:  files nis dns

The nfs server has already put in /etc/hosts file.

The lag on the very first try to mount is still there.


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Do system V init scripts work in LX Brand?

[Fred Liu]

2016-05-17 16:30 GMT+08:00 Fred Liu <fred.f...@gmail.com>:
> 2016-05-17 15:41 GMT+08:00 Chris Ridd <chrisr...@mac.com>:
>>
>>> On 17 May 2016, at 08:25, Fred Liu <fred.f...@gmail.com> wrote:
>>>
>>> 2016-05-17 15:10 GMT+08:00 Chris Ridd <chrisr...@mac.com>:
>>>>
>>>>> On 17 May 2016, at 07:40, Fred Liu <fred.f...@gmail.com> wrote:
>>>>>
>>>>> 2016-05-17 14:32 GMT+08:00 Joshua M. Clulow <j...@sysmgr.org>:
>>>>>> On 16 May 2016 at 23:29, Fred Liu <fred.f...@gmail.com> wrote:
>>>>>>> I have no success to boot the system V init scripts.
>>>>>>> Any success here?
>>>>>>
>>>>>> Can you give us a bit more detail about what you're doing?  Is this a
>>>>>> custom script you have added to your machine?  Is it in the global
>>>>>> zone of your SmartOS host, or in a SmartOS or LX-branded zone?  At
>>>>>> what path did you install the file?
>>>>>>
>>>>>>
>>>>>> Cheers.
>>>>>>
>>>>>
>>>>> We are running (CentOS 6.7 20151005) LX Brand. It is a custom script.
>>>>> I installed it on /etc/init.d/iqs. It is just a simple sh script:
>>>>
>>>> Add “set -x” near the start of the script and find out where it is failing.
>>>>
>>>
>>> It can be started manually  with no problems.
>>> The issue it can't be automatically started when we reboot LX Brand.
>>> Because the boot process is totally different in LX Brand.
>>> So the question converts to how to debug the boot process in LX Brand.
>>
>> OK, that’s some useful extra detail. Does something even *try* to run your 
>> script? Have you used chkconfig to enable it for the right Linux run levels? 
>> Maybe the LX zone isn’t in the run level you think it is.
>>
>> I would have thought that set -x could still be helpful if the output is 
>> captured in a system log which you can look at later. (I don’t recall what 
>> Linux does.) Or echo something into a tmp file, and see if that gets written 
>> during the boot.
>>
>
> Added "-x" and rebooted.
> /var/log/message:
>
> May 17 16:26:56 sha01 init: tty (console) main process (3698) killed
> by TERM signal
> May 17 16:26:57 sha01 xinetd[3549]: Exiting...
> May 17 16:27:19 sha01 rpcbind: rpcbind terminating on signal. Restart
> with "rpcbind -w"
> May 17 16:27:20 sha01 kernel: Kernel logging (proc) stopped.
> May 17 16:27:20 sha01 rsyslogd: [origin software="rsyslogd"
> swVersion="5.8.10" x-pid="3374" x-info="http://www.rsyslog.com;]
> exiting on signal 15.
> May 17 16:27:26 sha01 kernel: imklog 5.8.10, log source = /proc/kmsg started.
> May 17 16:27:26 sha01 rsyslogd: [origin software="rsyslogd"
> swVersion="5.8.10" x-pid="4476" x-info="http://www.rsyslog.com;] start
> May 17 16:27:26 sha01 rpc.statd[4520]: Version 1.2.3 starting
> May 17 16:27:26 sha01 sm-notify[4521]: Version 1.2.3 starting
> May 17 16:27:26 sha01 ypbind[4566]: Connection to D-BUS system message
> bus failed: Failed to connect to socket
> /var/run/dbus/system_bus_socket: No such file or directory.
> May 17 16:27:28 sha01 ypbind: NIS domain: issish, NIS server: cn07
> May 17 16:27:30 sha01 xinetd[4675]: xinetd Version 2.3.14 started with
> libwrap loadavg labeled-networking options compiled in.
> May 17 16:27:30 sha01 xinetd[4675]: Started working: 1 available service
>
> Seems nothing special.
>
> Thanks.
>

After 2-3 minutes, it finally works!
I am sure it is related to the issue that there is a lag on the very
first try to mount nfs v3 path in Linux Brand.

Anyway, many thanks for your nice help!!

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Do system V init scripts work in LX Brand?

[Fred Liu]

2016-05-17 15:41 GMT+08:00 Chris Ridd <chrisr...@mac.com>:
>
>> On 17 May 2016, at 08:25, Fred Liu <fred.f...@gmail.com> wrote:
>>
>> 2016-05-17 15:10 GMT+08:00 Chris Ridd <chrisr...@mac.com>:
>>>
>>>> On 17 May 2016, at 07:40, Fred Liu <fred.f...@gmail.com> wrote:
>>>>
>>>> 2016-05-17 14:32 GMT+08:00 Joshua M. Clulow <j...@sysmgr.org>:
>>>>> On 16 May 2016 at 23:29, Fred Liu <fred.f...@gmail.com> wrote:
>>>>>> I have no success to boot the system V init scripts.
>>>>>> Any success here?
>>>>>
>>>>> Can you give us a bit more detail about what you're doing?  Is this a
>>>>> custom script you have added to your machine?  Is it in the global
>>>>> zone of your SmartOS host, or in a SmartOS or LX-branded zone?  At
>>>>> what path did you install the file?
>>>>>
>>>>>
>>>>> Cheers.
>>>>>
>>>>
>>>> We are running (CentOS 6.7 20151005) LX Brand. It is a custom script.
>>>> I installed it on /etc/init.d/iqs. It is just a simple sh script:
>>>
>>> Add “set -x” near the start of the script and find out where it is failing.
>>>
>>
>> It can be started manually  with no problems.
>> The issue it can't be automatically started when we reboot LX Brand.
>> Because the boot process is totally different in LX Brand.
>> So the question converts to how to debug the boot process in LX Brand.
>
> OK, that’s some useful extra detail. Does something even *try* to run your 
> script? Have you used chkconfig to enable it for the right Linux run levels? 
> Maybe the LX zone isn’t in the run level you think it is.
>
> I would have thought that set -x could still be helpful if the output is 
> captured in a system log which you can look at later. (I don’t recall what 
> Linux does.) Or echo something into a tmp file, and see if that gets written 
> during the boot.
>

Added "-x" and rebooted.
/var/log/message:

May 17 16:26:56 sha01 init: tty (console) main process (3698) killed
by TERM signal
May 17 16:26:57 sha01 xinetd[3549]: Exiting...
May 17 16:27:19 sha01 rpcbind: rpcbind terminating on signal. Restart
with "rpcbind -w"
May 17 16:27:20 sha01 kernel: Kernel logging (proc) stopped.
May 17 16:27:20 sha01 rsyslogd: [origin software="rsyslogd"
swVersion="5.8.10" x-pid="3374" x-info="http://www.rsyslog.com;]
exiting on signal 15.
May 17 16:27:26 sha01 kernel: imklog 5.8.10, log source = /proc/kmsg started.
May 17 16:27:26 sha01 rsyslogd: [origin software="rsyslogd"
swVersion="5.8.10" x-pid="4476" x-info="http://www.rsyslog.com;] start
May 17 16:27:26 sha01 rpc.statd[4520]: Version 1.2.3 starting
May 17 16:27:26 sha01 sm-notify[4521]: Version 1.2.3 starting
May 17 16:27:26 sha01 ypbind[4566]: Connection to D-BUS system message
bus failed: Failed to connect to socket
/var/run/dbus/system_bus_socket: No such file or directory.
May 17 16:27:28 sha01 ypbind: NIS domain: issish, NIS server: cn07
May 17 16:27:30 sha01 xinetd[4675]: xinetd Version 2.3.14 started with
libwrap loadavg labeled-networking options compiled in.
May 17 16:27:30 sha01 xinetd[4675]: Started working: 1 available service

Seems nothing special.

Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Do system V init scripts work in LX Brand?

[Fred Liu]

2016-05-17 15:10 GMT+08:00 Chris Ridd <chrisr...@mac.com>:
>
>> On 17 May 2016, at 07:40, Fred Liu <fred.f...@gmail.com> wrote:
>>
>> 2016-05-17 14:32 GMT+08:00 Joshua M. Clulow <j...@sysmgr.org>:
>>> On 16 May 2016 at 23:29, Fred Liu <fred.f...@gmail.com> wrote:
>>>> I have no success to boot the system V init scripts.
>>>> Any success here?
>>>
>>> Can you give us a bit more detail about what you're doing?  Is this a
>>> custom script you have added to your machine?  Is it in the global
>>> zone of your SmartOS host, or in a SmartOS or LX-branded zone?  At
>>> what path did you install the file?
>>>
>>>
>>> Cheers.
>>>
>>
>> We are running (CentOS 6.7 20151005) LX Brand. It is a custom script.
>> I installed it on /etc/init.d/iqs. It is just a simple sh script:
>
> Add “set -x” near the start of the script and find out where it is failing.
>

It can be started manually  with no problems.
The issue it can't be automatically started when we reboot LX Brand.
Because the boot process is totally different in LX Brand.
So the question converts to how to debug the boot process in LX Brand.

Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Do system V init scripts work in LX Brand?

[Fred Liu]

2016-05-17 14:32 GMT+08:00 Joshua M. Clulow <j...@sysmgr.org>:
> On 16 May 2016 at 23:29, Fred Liu <fred.f...@gmail.com> wrote:
>> I have no success to boot the system V init scripts.
>> Any success here?
>
> Can you give us a bit more detail about what you're doing?  Is this a
> custom script you have added to your machine?  Is it in the global
> zone of your SmartOS host, or in a SmartOS or LX-branded zone?  At
> what path did you install the file?
>
>
> Cheers.
>

We are running (CentOS 6.7 20151005) LX Brand. It is a custom script.
I installed it on /etc/init.d/iqs. It is just a simple sh script:

#!/bin/sh

# start and stop iqs exec daemon   #


# Basic support for RedHat style chkconfig
#
# chkconfig: - 99 01
# description: Starts and stops the iqs exec daemon.
#
### BEGIN INIT INFO
# Provides:  iqs
# Required-Start: $remote_fs $all
# Should-Start:
# Required-Stop:
# Default-Start:  2 3 5
# Default-Stop:   0 6
# Description:Starts and stops iqs exec daemon.
### END INIT INFO

start()
{
  echo "Trying to start iqs exec daemon:"
  su  admin -c "/tool/iqs/bin/execd.py start"
}

stop()
{
  echo "Trying to stop iqs exec daemon:"
  su admin -c "/tool/iqs/bin/execd.py stop"
}case "$1" in
'start')
  start
  if [ -d /var/lock/subsys ]; then
touch /var/lock/subsys/iqs
  elif [ -d /var/lock ]; then
touch /var/lock/iqs
  fi
  ;;

'stop')
stop
if [ -d /var/lock/subsys ]; then
  rm -f /var/lock/subsys/iqs
elif [ -d /var/lock ]; then
  rm -f /var/lock/iqs
fi
  ;;

'restart')
restart
  ;;
*)
  echo "Usage: $0 {start|stop|restart}"
  exit 1
  ;;
esac

BTW, it works in normal Linux OS.

Thanks.

Fred



Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] Do system V init scripts work in LX Brand?

[Fred Liu]

Hi,

I have no success to boot the system V init scripts.
Any success here?

Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Re: Any possibilities in python OSError?

[Fred Liu]

2016-05-16 21:44 GMT+08:00 Richard Elling <richard.ell...@richardelling.com>:
>
>> On May 16, 2016, at 3:40 AM, Fred Liu <fred.f...@gmail.com> wrote:
>>
>> It could be the slow read from the nfs path -- "/tool/iqs/run".
>> We see nfs v4 client not working in LX brand(I have already opened OS-5265).
>> And nfs v3 client is working but it has obvious lag( about 5-10
>> seconds) at the very first try to mount nfs path.
>> As long as the mount is done, there is no obvious lag in coming
>> nfs-related operations.
>> And further, we find if SmartOS where LX brands are living in serve
>> nfs service, the lag won't appear.
>> It could be something happened in network path.
>
> this is consistent with name lookup timeout. double check dns, ldap, and all 
> other name sources.
>

I check  /etc/nsswitch.conf and I get following:
hosts:  files nis dns

The nfs server has already been put in /etc/hosts file.

The lag on the very first try to mount is still there.


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] Any possibilities in python OSError?

[Fred Liu]

Hi,

We are running some python scripts in LX brand (CentOS 6.7 20151005).
And we get following errors:

File "/tool/iqs/bin/execd.py", line 416, in polljob
runfiles = [int(f) for f in os.listdir(RUNDIR) if f.isdigit()]
exceptions.OSError: [Errno 4] Interrupted system call: '/tool/iqs/run'



They have been running well under normal Linux OS.

Any possibilities?


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [discuss] zfs send -r would be nice

[Fred Liu]

> -Original Message-
> From: Gabriele Bulfon [mailto:gbul...@sonicle.com]
> Sent: 星期日, 五月 08, 2016 20:45
> To: Jim Klimov; discuss@lists.illumos.org
> Cc: Paul Dagnelie; Matthew Ahrens
> Subject: Re: [discuss] zfs send -r would be nice
> 
> :) Clones are another storyusually not there in CIFS shares, which are the
> ones to be attacked by windows crypto lockers... ;)
> 
> Thanx for the pointer though, nice one to not reinvent the wheel ;) But I 
> still
> believe zfs bare options are missing the need to replicate an fs subtree 
> exactly,
> but without previous snapshots.
> 

-r is already implemented in solaris 11.2:

-r

 Generates a recursive stream  package.  A  recursive
 stream  package  contains  a  series  of full and/or
 incremental streams. When received,  all  properties
 and  descendent  file  systems are preserved. Unlike
 with the replication stream packages generated  with
 the   -R   flag,   intermediate  snapshots  are  not
 preserved unless the intermediate  snapshot  is  the
 origin of a clone that is included in the stream.

Thanks.


Fred


---
illumos-discuss
Archives: https://www.listbox.com/member/archive/182180/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=21175430_secret=21175430-6a77cda4
Powered by Listbox: http://www.listbox.com

Re: [OmniOS-discuss] 4kn or 512e with ashift=12

[Fred Liu]

> -Original Message-
> From: Fred Liu
> Sent: 星期四, 三月 24, 2016 18:26
> To: 'Chris Siebenmann'; Richard Jahnel
> Cc: omnios-discuss@lists.omniti.com
> Subject: RE: [OmniOS-discuss] 4kn or 512e with ashift=12
> 
> 
> 
> > -Original Message-
> > From: Chris Siebenmann [mailto:c...@cs.toronto.edu]
> > Sent: 星期三, 三月 23, 2016 23:33
> > To: Richard Jahnel
> > Cc: Chris Siebenmann; Fred Liu; omnios-discuss@lists.omniti.com
> > Subject: Re: [OmniOS-discuss] 4kn or 512e with ashift=12
> >
> > > It should be noted that using a 512e disk as a 512n disk subjects
> > > you to a significant risk of silent corruption in the event of power loss.
> > > Because 512e disks does a read>modify>write operation to modify
> > > 512byte chunk of a 4k sector, zfs won't know about the other
> > > 7 corrupted 512e sectors in the event of a power loss during a write
> > > operation. So when discards the incomplete txg on reboot, it won't
> > > do anything about the other 7 512e sectors it doesn't know were affected.
> >
> >  This is true; under normal circumstances you do not want to use a
> > 512e drive in an ashift=9 vdev. However, if you have a dead 512n drive
> > and you have no remaining 512n spares, your choices are to run without
> > redundancy, to wedge in a 512e drive and accept the potential problems
> > on power failure (problems that can likely be fixed by scrubbing the
> > pool afterwards), or obtain enough additional drives (and perhaps
> > server(s)) to entirely rebuild the pool on 512e drives with ashift=12.
> >
> >  In this situation, running with a 512e drive and accepting the
> > performance issues and potential exposure to power failures is
> > basically the lesser evil. (I wish ZFS was willing to accept this, but
> > it isn't.)
> >
> [Fred Liu]: I have a similar test here:
> 
> [root@00-25-90-74-f5-04 ~]# zpool status
>   pool: tank
>  state: ONLINE
>   scan: resilvered 187G in 21h9m with 0 errors on Thu Jan 15 08:05:16 2015
> config:
> 
> NAME STATE READ WRITE CKSUM
> tank ONLINE   0 0 0
>   raidz2-0   ONLINE   0 0 0
> c2t45d0  ONLINE   0 0 0
> c2t46d0  ONLINE   0 0 0
> c2t47d0  ONLINE   0 0 0
> c2t48d0  ONLINE   0 0 0
> c2t49d0  ONLINE   0 0 0
> c2t52d0  ONLINE   0 0 0
> c2t53d0  ONLINE   0 0 0
> c2t44d0  ONLINE   0 0 0
> spares
>   c0t5000CCA6A0C791CBd0  AVAIL
> 
> errors: No known data errors
> 
>   pool: zones
>  state: ONLINE
>   scan: scrub repaired 0 in 2h45m with 0 errors on Tue Aug 12 20:24:30 2014
> config:
> 
> NAME   STATE READ WRITE CKSUM
> zones  ONLINE   0 0 0
>   raidz2-0 ONLINE   0 0 0
> c0t5000C500584AC07Bd0  ONLINE   0 0 0
> c0t5000C500584AC557d0  ONLINE   0 0 0
> c0t5000C500584ACB1Fd0  ONLINE   0 0 0
> c0t5000C500584AD7B3d0  ONLINE   0 0 0
> c0t5000C500584C30DBd0  ONLINE   0 0 0
> c0t5000C500586E54A3d0  ONLINE   0 0 0
> c0t5000C500586EF0CBd0  ONLINE   0 0 0
> c0t5000C50058426A0Fd0  ONLINE   0 0 0
> logs
>   c4t0d0   ONLINE   0 0 0
>   c4t1d0   ONLINE   0 0 0
> cache
>   c0t55CD2E404BE9CB7Ed0ONLINE   0 0 0
> 
> errors: No known data errors
> 
> [root@00-25-90-74-f5-04 ~]# format
> Searching for disks...done
> 
> 
> AVAILABLE DISK SELECTIONS:
>0. c0t55CD2E404BE9CB7Ed0  SSDSC2BW18-DC32-167.68GB>
>   /scsi_vhci/disk@g55cd2e404be9cb7e
>1. c0t5000C500584AC07Bd0
> 
>   /scsi_vhci/disk@g5000c500584ac07b
>2. c0t5000C500584AC557d0
> 
>   /scsi_vhci/disk@g5000c500584ac557
>3. c0t5000C500584ACB1Fd0
> 
>   /scsi_vhci/disk@g5000c500584acb1f
>4. c0t5000C500584AD7B3d0
> 
>   /scsi_vhci/disk@g5000c500584ad7b3
>5. c0t5000C500584C30DBd0
> 
>   /scsi_vhci/disk@g5000c500584c30db
>6. c0t5000C500586E54A3d0
> 
>   /scsi_vhci/disk@g5000c500586e54a3

Re: [OmniOS-discuss] 4kn or 512e with ashift=12

[Fred Liu]

> -Original Message-
> From: Fred Liu
> Sent: 星期一, 三月 28, 2016 16:57
> To: 'Chris Siebenmann'; 'Richard Jahnel'
> Cc: 'omnios-discuss@lists.omniti.com'
> Subject: RE: [OmniOS-discuss] 4kn or 512e with ashift=12
>
>
>
> > -Original Message-
> > From: Fred Liu
> > Sent: 星期四, 三月 24, 2016 18:26
> > To: 'Chris Siebenmann'; Richard Jahnel
> > Cc: omnios-discuss@lists.omniti.com
> > Subject: RE: [OmniOS-discuss] 4kn or 512e with ashift=12
> >
> >
> >
> > > -Original Message-
> > > From: Chris Siebenmann [mailto:c...@cs.toronto.edu]
> > > Sent: 星期三, 三月 23, 2016 23:33
> > > To: Richard Jahnel
> > > Cc: Chris Siebenmann; Fred Liu; omnios-discuss@lists.omniti.com
> > > Subject: Re: [OmniOS-discuss] 4kn or 512e with ashift=12
> > >
> > > > It should be noted that using a 512e disk as a 512n disk subjects
> > > > you to a significant risk of silent corruption in the event of power 
> > > > loss.
> > > > Because 512e disks does a read>modify>write operation to modify
> > > > 512byte chunk of a 4k sector, zfs won't know about the other
> > > > 7 corrupted 512e sectors in the event of a power loss during a
> > > > write operation. So when discards the incomplete txg on reboot, it
> > > > won't do anything about the other 7 512e sectors it doesn't know were
> affected.
> > >
> > >  This is true; under normal circumstances you do not want to use a
> > > 512e drive in an ashift=9 vdev. However, if you have a dead 512n
> > > drive and you have no remaining 512n spares, your choices are to run
> > > without redundancy, to wedge in a 512e drive and accept the
> > > potential problems on power failure (problems that can likely be
> > > fixed by scrubbing the pool afterwards), or obtain enough additional
> > > drives (and perhaps
> > > server(s)) to entirely rebuild the pool on 512e drives with ashift=12.
> > >
> > >  In this situation, running with a 512e drive and accepting the
> > > performance issues and potential exposure to power failures is
> > > basically the lesser evil. (I wish ZFS was willing to accept this,
> > > but it isn't.)
> > >
> > [Fred Liu]: I have a similar test here:
> >
> > [root@00-25-90-74-f5-04 ~]# zpool status
> >   pool: tank
> >  state: ONLINE
> >   scan: resilvered 187G in 21h9m with 0 errors on Thu Jan 15 08:05:16
> > 2015
> > config:
> >
> > NAME STATE READ WRITE CKSUM
> > tank ONLINE   0 0 0
> >   raidz2-0   ONLINE   0 0 0
> > c2t45d0  ONLINE   0 0 0
> > c2t46d0  ONLINE   0 0 0
> > c2t47d0  ONLINE   0 0 0
> > c2t48d0  ONLINE   0 0 0
> > c2t49d0  ONLINE   0 0 0
> > c2t52d0  ONLINE   0 0 0
> > c2t53d0  ONLINE   0 0 0
> > c2t44d0  ONLINE   0 0 0
> > spares
> >   c0t5000CCA6A0C791CBd0  AVAIL
> >
> > errors: No known data errors
> >
> >   pool: zones
> >  state: ONLINE
> >   scan: scrub repaired 0 in 2h45m with 0 errors on Tue Aug 12 20:24:30
> > 2014
> > config:
> >
> > NAME   STATE READ WRITE
> CKSUM
> > zones  ONLINE   0 0 0
> >   raidz2-0 ONLINE   0 0 0
> > c0t5000C500584AC07Bd0  ONLINE   0 0 0
> > c0t5000C500584AC557d0  ONLINE   0 0 0
> > c0t5000C500584ACB1Fd0  ONLINE   0 0 0
> > c0t5000C500584AD7B3d0  ONLINE   0 0 0
> > c0t5000C500584C30DBd0  ONLINE   0 0 0
> > c0t5000C500586E54A3d0  ONLINE   0 0 0
> > c0t5000C500586EF0CBd0  ONLINE   0 0 0
> > c0t5000C50058426A0Fd0  ONLINE   0 0 0
> > logs
> >   c4t0d0   ONLINE   0 0 0
> >   c4t1d0   ONLINE   0 0 0
> > cache
> >   c0t55CD2E404BE9CB7Ed0ONLINE   0 0 0
> >
> > errors: No known data errors
> >
> > [root@00-25-90-74-f5-04 ~]# format
>

[smartos-discuss] RE: [developer] HBA recommended except LSI and ARECA

[Fred Liu]

> -Original Message-
> From: Fred Liu
> Sent: 星期二, 五月 06, 2014 12:22
> To: Zhiwen Zheng; Keith Wesolowski
> Cc: omnios-disc...@lists.omniti.com; Discussion list for OpenIndiana; Fred 
> Liu;
> develo...@lists.illumos.org; smartos-discuss@lists.smartos.org
> Subject: RE: [developer] HBA recommended except LSI and ARECA
> 
> 
> >From: Zhiwen Zheng [mailto:zhiwen...@gmail.com]
> >Sent: 星期二, 五月 06, 2014 10:09
> >To: Keith Wesolowski
> >Cc: omnios-disc...@lists.omniti.com; Fred Liu; Discussion list for
> OpenIndiana; Fred Liu; develo...@lists.illumos.org;
> smartos-discuss@lists.smartos.org
> >Subject: Re: [developer] HBA recommended except LSI and ARECA
> 
> >Hi,
> >I get an Adaptec card several days ago, the pci id changed, after add the new
> pci id, pmcs still can not attach.
> >I checked the linux pm8001 driver,
> >it seems to access some registers, pci bar 4 address need to be shifted.
> >I am out of door now,  I think I can try to fix this several days later.
> 
> "prtconf -D" has no info about pm8001. "prtconf -vvv" will get only following
> info:
> 
> name='vendor-id' type=int items=1
> value=9005
> name='device-id' type=int items=1
> value=8081
> name='vendor-name' type=string items=1
> value='Adaptec'
> name='device-name' type=string items=1
> value='PMC-Sierra PM8001 SAS HBA [Series 6H]'
> name='subsystem-name' type=string items=1
> value='unknown subsystem'
> 
> And yes, pmcs doen't attach.

Any progress so far?

Thanks.

Fred



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [OpenIndiana-discuss] [developer] HBA recommended except LSI and ARECA

[Fred Liu]

> -Original Message-
> From: Fred Liu
> Sent: 星期二, 五月 06, 2014 12:22
> To: Zhiwen Zheng; Keith Wesolowski
> Cc: omnios-disc...@lists.omniti.com; Discussion list for OpenIndiana; Fred 
> Liu;
> develo...@lists.illumos.org; smartos-disc...@lists.smartos.org
> Subject: RE: [developer] HBA recommended except LSI and ARECA
> 
> 
> >From: Zhiwen Zheng [mailto:zhiwen...@gmail.com]
> >Sent: 星期二, 五月 06, 2014 10:09
> >To: Keith Wesolowski
> >Cc: omnios-disc...@lists.omniti.com; Fred Liu; Discussion list for
> OpenIndiana; Fred Liu; develo...@lists.illumos.org;
> smartos-disc...@lists.smartos.org
> >Subject: Re: [developer] HBA recommended except LSI and ARECA
> 
> >Hi,
> >I get an Adaptec card several days ago, the pci id changed, after add the new
> pci id, pmcs still can not attach.
> >I checked the linux pm8001 driver,
> >it seems to access some registers, pci bar 4 address need to be shifted.
> >I am out of door now,  I think I can try to fix this several days later.
> 
> "prtconf -D" has no info about pm8001. "prtconf -vvv" will get only following
> info:
> 
> name='vendor-id' type=int items=1
> value=9005
> name='device-id' type=int items=1
> value=8081
> name='vendor-name' type=string items=1
> value='Adaptec'
> name='device-name' type=string items=1
> value='PMC-Sierra PM8001 SAS HBA [Series 6H]'
> name='subsystem-name' type=string items=1
> value='unknown subsystem'
> 
> And yes, pmcs doen't attach.

Any progress so far?

Thanks.

Fred

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OmniOS-discuss] 4kn or 512e with ashift=12

[Fred Liu]

> -Original Message-
> From: Chris Siebenmann [mailto:c...@cs.toronto.edu]
> Sent: 星期三, 三月 23, 2016 23:33
> To: Richard Jahnel
> Cc: Chris Siebenmann; Fred Liu; omnios-discuss@lists.omniti.com
> Subject: Re: [OmniOS-discuss] 4kn or 512e with ashift=12
> 
> > It should be noted that using a 512e disk as a 512n disk subjects you
> > to a significant risk of silent corruption in the event of power loss.
> > Because 512e disks does a read>modify>write operation to modify
> > 512byte chunk of a 4k sector, zfs won't know about the other
> > 7 corrupted 512e sectors in the event of a power loss during a write
> > operation. So when discards the incomplete txg on reboot, it won't do
> > anything about the other 7 512e sectors it doesn't know were affected.
> 
>  This is true; under normal circumstances you do not want to use a 512e drive
> in an ashift=9 vdev. However, if you have a dead 512n drive and you have no
> remaining 512n spares, your choices are to run without redundancy, to wedge
> in a 512e drive and accept the potential problems on power failure (problems
> that can likely be fixed by scrubbing the pool afterwards), or obtain enough
> additional drives (and perhaps
> server(s)) to entirely rebuild the pool on 512e drives with ashift=12.
> 
>  In this situation, running with a 512e drive and accepting the performance
> issues and potential exposure to power failures is basically the lesser evil. 
> (I
> wish ZFS was willing to accept this, but it isn't.)
> 
[Fred Liu]: I have a similar test here:

[root@00-25-90-74-f5-04 ~]# zpool status
  pool: tank
 state: ONLINE
  scan: resilvered 187G in 21h9m with 0 errors on Thu Jan 15 08:05:16 2015
config:

NAME STATE READ WRITE CKSUM
tank ONLINE   0 0 0
  raidz2-0   ONLINE   0 0 0
c2t45d0  ONLINE   0 0 0
c2t46d0  ONLINE   0 0 0
c2t47d0  ONLINE   0 0 0
c2t48d0  ONLINE   0 0 0
c2t49d0  ONLINE   0 0 0
c2t52d0  ONLINE   0 0 0
c2t53d0  ONLINE   0 0 0
c2t44d0  ONLINE   0 0 0
spares
  c0t5000CCA6A0C791CBd0  AVAIL

errors: No known data errors

  pool: zones
 state: ONLINE
  scan: scrub repaired 0 in 2h45m with 0 errors on Tue Aug 12 20:24:30 2014
config:

NAME   STATE READ WRITE CKSUM
zones  ONLINE   0 0 0
  raidz2-0 ONLINE   0 0 0
c0t5000C500584AC07Bd0  ONLINE   0 0 0
c0t5000C500584AC557d0  ONLINE   0 0 0
c0t5000C500584ACB1Fd0  ONLINE   0 0 0
c0t5000C500584AD7B3d0  ONLINE   0 0 0
c0t5000C500584C30DBd0  ONLINE   0 0 0
c0t5000C500586E54A3d0  ONLINE   0 0 0
c0t5000C500586EF0CBd0  ONLINE   0 0 0
c0t5000C50058426A0Fd0  ONLINE   0 0 0
logs
  c4t0d0   ONLINE   0 0 0
  c4t1d0   ONLINE   0 0 0
cache
  c0t55CD2E404BE9CB7Ed0ONLINE   0 0 0

errors: No known data errors

[root@00-25-90-74-f5-04 ~]# format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
   0. c0t55CD2E404BE9CB7Ed0 
  /scsi_vhci/disk@g55cd2e404be9cb7e
   1. c0t5000C500584AC07Bd0 
  /scsi_vhci/disk@g5000c500584ac07b
   2. c0t5000C500584AC557d0 
  /scsi_vhci/disk@g5000c500584ac557
   3. c0t5000C500584ACB1Fd0 
  /scsi_vhci/disk@g5000c500584acb1f
   4. c0t5000C500584AD7B3d0 
  /scsi_vhci/disk@g5000c500584ad7b3
   5. c0t5000C500584C30DBd0 
  /scsi_vhci/disk@g5000c500584c30db
   6. c0t5000C500586E54A3d0 
  /scsi_vhci/disk@g5000c500586e54a3
   7. c0t5000C500586EF0CBd0 
  /scsi_vhci/disk@g5000c500586ef0cb
   8. c0t5000C50058426A0Fd0 
  /scsi_vhci/disk@g5000c50058426a0f
   9. c0t5000CCA6A0C791CBd0 
  /scsi_vhci/disk@g5000cca6a0c791cb
  10. c0t5F0056425331d0 
  /scsi_vhci/disk@g5f0056425331
  11. c2t44d0 
  /pci@0,0/pci8086,1c10@1c/pci1000,3140@0/sd@2c,0
  12. c2t45d0 
  /pci@0,0/pci8086,1c10@1c/pci1000,3140@0/sd@2d,0
  13. c2t46d0 
  /pci@0,0/pci8086,1c10@1c/pci1000,3140@0/sd@2e,0
  14. c2t47d0 
  /pci@0,0/pci8086,1c10@1c/pci1000,3140@0/sd@2f,0
  15. c2t48d0 
  /pci@0,0/pci8086,1c10@1c/pci1000,3140@0/sd@30,0
  16. c2t49d0 
  /pci@0,0/pci8086,1c10@1c/pci1000,3140@0/sd@31,0
   

Re: [OmniOS-discuss] 4kn or 512e with ashift=12

[Fred Liu]

> -Original Message-
> From: Richard Elling [mailto:richard.ell...@richardelling.com]
> Sent: 星期三, 三月 23, 2016 4:53
> To: Chris Siebenmann
> Cc: Fred Liu; omnios-discuss@lists.omniti.com
> Subject: Re: [OmniOS-discuss] 4kn or 512e with ashift=12
> 
> 
>   On Mar 22, 2016, at 7:41 AM, Chris Siebenmann <c...@cs.toronto.edu
> <mailto:c...@cs.toronto.edu> > wrote:
> 
> 
>   This implicitly assumes that the only reason to set 
> ashift=12 is
>   if you are currently using one or more drives that 
> require it. I
>   strongly disagree with this view. Since ZFS cannot 
> currently
> replace
>   a 512n drive with a 512e one, I feel [...]
> 
> 
> 
>   *In theory* this replacement should work well if the lie works
> *correctly*.
>   In ZoL, for the "-o ashift" is supported in "zpool replace", the
>   replacement should also work in mixed sector sizes.
>   And in illumos the whitelist will do the same.
>   What errors have you ever seen?
> 
> 
> 
>   We have seen devices that changed between (claimed) 512n and
>   (claimed) 512e/4k *within the same model number*; the only thing that
>   distinguished the two was firmware version (which is not something that
>   you can match in sd.conf). This came as a complete surprise to us the
>   first time we needed to replace an old (512n) one of these with a new
>   (512e) one.
> 
>   The sd.conf whitelist also requires a reboot to activate if you need
>   to add a new entry, as far as I know.
> 
>   (Nor do I know what happens if you have some 512n disks and some
>   512e disks, both correctly recognized and in different pools, and
>   now you need to replace a 512n disk with a spare 512e disk so you
>   change sd.conf to claim that all of the 512e disks are 512n. I'd
>   like to think that ZFS will carry on as normal, but I'm not sure.
>   This makes it somewhat dangerous to change sd.conf on a live system.)

There are two cases if we don't use the remedy (whitelist in illumos or -o 
ashift in ZoL) here:
a): 512n <---> 512e. This replacement should work *in theory* if the lie works 
*correctly*.
b): 512n <-x-> 4kn.  This replacement may not work for the different physical 
sector sizes.

Your surprise may come from case b.
> 
> 
> 
> What is missing from
> http://wiki.illumos.org/display/illumos/ZFS+and+Advanced+Format+disks
> is:
> 
> 1. how to change the un_phy_blocksize for any or all uns 2. how to set a 
> default
> setting for all drives in sd.conf by setting attributes to
> the "<vid+pid>" of ""  (see sd(7d))
> 
> I am aware of no new HDDs with 512n, so this problem will go away for HDDs.
> However, there are many SSDs that work better with un_phy_blocksize = 8192
> and some vendors set sd.conf or source appropriately.
>  -- richard
> 
> 
> 
>   For many usage cases, somewhat more space usage and
> perhaps
>   somewhat slower pools are vastly preferable to a loss 
> of pool
>   redundancy over time. I feel that OmniOS should at 
> least give
> you
>   the option here (in a less crude way than simply 
> telling it that
>   absolutely all of your drives are 4k drives, partly 
> because such
>   general lies are problematic in various situations).
> 
> 
> 
>   The whitelist (sd.conf) should fit into this consideration. But 
> not
>   sure how mixed sector sizes impact the performance.
> 
> 
> 
>   Oh, 512e disks in a 512n pool will probably have not great performance.
>   ZFS does a lot of unaligned reads and writes, unlike other filesystems;
>   if you say your disks are 512n, it really believes you and behaves
>   accordingly.

I am just curious about if the mixed sector sizes(512n+4kn) will impact 
performance.

Thanks.

Fred
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] 4kn or 512e with ashift=12

[Fred Liu]

> -Original Message-
> From: OmniOS-discuss [mailto:omnios-discuss-boun...@lists.omniti.com] On
> Behalf Of Richard Elling
> Sent: 星期二, 三月 22, 2016 3:19
> To: Richard Jahnel
> Cc: omnios-discuss@lists.omniti.com
> Subject: Re: [OmniOS-discuss] 4kn or 512e with ashift=12
> 
> 
> > On Mar 21, 2016, at 12:00 PM, Richard Jahnel 
> wrote:
> >
> > Both approaches have their error points.
> >
> > FWIW I would very very much like to be able to force my new pools into
> ashift=12. It would make drive purchasing and replacement a lot more straight
> forward and future resistant.
> 
> The fundamental problem is that this is a vdev-settable, not a pool settable.
> Today, it is very common for pools to have multiple ashifts active. Recently,
> per-vdev ZAP objects have been proposed and that code is working its way
> through the review and integration process.

Not sure how multiple-ashifts impact the performace.
> 
> Meanwhile, use one or more of the dozens of methods documented for doing
> this.
> 
> FWIW, most people with HDDs want space efficiency, because HDDs lost the
> performance race to SSDs long ago. In general, forcing everything to 4k 
> reduces
> space efficiency, so it is unlikely to be a good default.

Agree.

Thanks.

Fred
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] 4kn or 512e with ashift=12

[Fred Liu]

> -Original Message-
> From: OmniOS-discuss [mailto:omnios-discuss-boun...@lists.omniti.com] On
> Behalf Of Richard Elling
> Sent: 星期二, 三月 22, 2016 3:21
> To: Bob Friesenhahn
> Cc: omnios-discuss@lists.omniti.com
> Subject: Re: [OmniOS-discuss] 4kn or 512e with ashift=12
> 
> 
> > On Mar 21, 2016, at 12:19 PM, Bob Friesenhahn
>  wrote:
> >
> > On Mon, 21 Mar 2016, Richard Elling wrote:
> >>>
> >>> Adding the ashift argument to zpool was discussed every few years and so
> far was always deemed not enterprisey enough for the Solaris heritage, so the
> setup to tweak sd driver reports and properly rely on that layer was pushed
> instead.
> >>
> >> The issue is that once a drive model lies, then the Solaris approach
> >> is to encode the lie into a whitelist, so that the lie is always
> >> handled properly. The whitelist is in the sd.conf file.
> >
> > Does this approach require that Illumos users only use drive hardware much
> older than the version of Illumos they happen running since outdated whitelist
> won't know about the new lies?
> 
> Forunately, lies are becoming less common. But this raises a good point: if 
> your
> drive doesn't lie, then you don't need to workaround.

That means 512n and 4kn are handled correctly by default, right?


Thanks.

Fred
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] 4kn or 512e with ashift=12

[Fred Liu]

> -Original Message-
> From: OmniOS-discuss [mailto:omnios-discuss-boun...@lists.omniti.com] On
> Behalf Of Hanno Hirschberger
> Sent: 星期一, 三月 21, 2016 17:02
> To: omnios-discuss@lists.omniti.com
> Subject: Re: [OmniOS-discuss] 4kn or 512e with ashift=12
> 
> On 21.03.2016 08:00, Fred Liu wrote:
> > So that means illumos can handle 512n and 4kn automatically and properly?
> 
> Not necessarily as far as I know. Sometime drives are emulating 512 blocks and
> don't properly tell the OS about that and Illumos ZFS is aligning the drives 
> with
> ashift=9 which leads to enormous performance issues. Also forcing the system

That is the goal(ashift=9) that 512e wants to realize. Isn't it? Emulation is 
to guarantee
compatiblity not performace, right?

> to handle drives with a specific sector size with the sd.conf doesn't turn 
> out to
> be reliable in some cases (at least on my workstations). Here's what I do to

What errors have you ever seen?

> ensure ashift=12 values:
> 
> Reboot the system with a Linux live disk of your choice and install ZoL in 
> the live
> session. Then create the ZFS pool, export it and reboot the machine. OmniOS /
> Illumos can import the new pool without problems and the ashift value is

This operation is driver-dependant. I have the similar workaround. It works for 
avago HBAs.
But it doesn't apply in NVMe drivers. The zpool comprised of NVMe SSDs created 
under ZoL can't be imported under Illumos
in my tests.

> correctly set. There was a fixed zpool binary (Solaris 11 binary) flying 
> around the
> internet which can handle the "-o shift=12" parameter and works with OmniOS
> but unfortunately I can't find it again right now. This would make the reboot
> into a live session obsolete.
> 
> Does anyone know if the "ashift" parameter will be implemented in the OmniOS
> / Illumos zpool binary in the near future?

I think the whitelist(sd.conf) is the choice by Illumos. But we may try build 
it ourselves if the source is available.

Thanks.

Fred 
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] 4kn or 512e with ashift=12

[Fred Liu]

> -Original Message-
> From: OmniOS-discuss [mailto:omnios-discuss-boun...@lists.omniti.com] On
> Behalf Of Jim Klimov
> Sent: 星期二, 三月 22, 2016 2:11
> To: Hanno Hirschberger; omnios-discuss@lists.omniti.com
> Subject: Re: [OmniOS-discuss] 4kn or 512e with ashift=12
> 
> 21 марта 2016 г. 10:02:03 CET, Hanno Hirschberger
> <hannohirschber...@googlemail.com> пишет:
> >On 21.03.2016 08:00, Fred Liu wrote:
> >> So that means illumos can handle 512n and 4kn automatically and
> >properly?
> >
> >Not necessarily as far as I know. Sometime drives are emulating 512
> >blocks and don't properly tell the OS about that and Illumos ZFS is
> >aligning the drives with ashift=9 which leads to enormous performance
> >issues. Also forcing the system to handle drives with a specific sector
> >
> >size with the sd.conf doesn't turn out to be reliable in some cases (at
> >
> >least on my workstations). Here's what I do to ensure ashift=12 values:
> >
> >Reboot the system with a Linux live disk of your choice and install ZoL
> >
> >in the live session. Then create the ZFS pool, export it and reboot the
> >
> >machine. OmniOS / Illumos can import the new pool without problems and
> >the ashift value is correctly set. There was a fixed zpool binary
> >(Solaris 11 binary) flying around the internet which can handle the "-o
> >
> >shift=12" parameter and works with OmniOS but unfortunately I can't
> >find it again right now. This would make the reboot into a live session
> >obsolete.
> >
> >Does anyone know if the "ashift" parameter will be implemented in the
> >OmniOS / Illumos zpool binary in the near future?
> >
> >Best regards
> >
> >Hanno
> >___
> >OmniOS-discuss mailing list
> >OmniOS-discuss@lists.omniti.com
> >http://lists.omniti.com/mailman/listinfo/omnios-discuss
> 
> Adding the ashift argument to zpool was discussed every few years and so far
> was always deemed not enterprisey enough for the Solaris heritage, so the
> setup to tweak sd driver reports and properly rely on that layer was pushed
> instead.
> 
> That said, the old tweaked binary came with a blog post detailing the source
> changes; you're welcome to try a d port and rti it (I'd say there is enough 
> user
> demand to back the non-enterprisey fix to be on par with other OpenZFS
> siblings). At worst, you can publish the modernized binary as the original
> blogger did ;)

Is the post/source still accessible?


Thanks.

Fred
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] 4kn or 512e with ashift=12

[Fred Liu]

> -Original Message-
> From: OmniOS-discuss [mailto:omnios-discuss-boun...@lists.omniti.com] On
> Behalf Of Chris Siebenmann
> Sent: 星期二, 三月 22, 2016 3:27
> To: Richard Elling
> Cc: omnios-discuss@lists.omniti.com
> Subject: Re: [OmniOS-discuss] 4kn or 512e with ashift=12
> 
> > > Adding the ashift argument to zpool was discussed every few years
> > > and so far was always deemed not enterprisey enough for the Solaris
> > > heritage, so the setup to tweak sd driver reports and properly rely
> > > on that layer was pushed instead.
> >
> > The issue is that once a drive model lies, then the Solaris approach
> > is to encode the lie into a whitelist, so that the lie is always
> > handled properly. The whitelist is in the sd.conf file.
> >
> > By contrast, the ZFSonLinux approach requires that the sysadmin knows
> > there is a lie and manually corrects for every invocation. This is
> > unfortunately a very error-prone approach.
> 
>  This implicitly assumes that the only reason to set ashift=12 is if you are
> currently using one or more drives that require it. I strongly disagree with 
> this
> view. Since ZFS cannot currently replace a 512n drive with a 512e one, I feel

*In theory* this replacement should work well if the lie works *correctly*.
 In ZoL, for the "-o ashift" is supported in "zpool replace", the replacement 
should also work in mixed sector sizes.
 And in illumos the whitelist will do the same.
 What errors have you ever seen?

> that you really want to force-create all pools with ashift=12 even on 512n 
> drives
> unless you're absolutely confident that you will be able to obtain replacement
> 512n drives over the lifetime of your pool (or unless the impact of using
> ashift=12 is so drastic on your usage case that you will need to totally 
> rethink
> your pool if you become unable to get 512n replacement drives).

Same as my comments above.
> 
>  For many usage cases, somewhat more space usage and perhaps somewhat
> slower pools are vastly preferable to a loss of pool redundancy over time. I 
> feel
> that OmniOS should at least give you the option here (in a less crude way than
> simply telling it that absolutely all of your drives are 4k drives, partly 
> because
> such general lies are problematic in various situations).
> 

The whitelist (sd.conf) should fit into this consideration. But not sure how 
mixed sector sizes impact the performance.


Thanks.

Fred
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] 4kn or 512e with ashift=12

[Fred Liu]

So that means illumos can handle 512n and 4kn automatically and properly?

Thanks.

Fred

From: Matej Žerovnik [mailto:ma...@zunaj.si]
Sent: 星期一, 三月 21, 2016 14:20
To: Fred Liu
Cc: geo...@gnaa.net; omnios-discuss; zfs-disc...@list.zfsonlinux.org
Subject: Re: [OmniOS-discuss] 4kn or 512e with ashift=12

You can’t do that, but you can force system to recognize hard drive as if it 
was 4Kn. Just like we do it for SSDs: 
http://wiki.illumos.org/display/illumos/List+of+sd-config-list+entries+for+Advanced-Format+drives

lp, Matej


On 21 Mar 2016, at 06:00, Fred Liu 
<fred_...@issi.com<mailto:fred_...@issi.com>> wrote:

So, you can “zpool create –o ashift=12” in illumos? I can’t do that in smartos 
at least….

From: Geoff Nordli [mailto:geoff.nor...@gmail.com] On Behalf Of Geoff Nordli
Sent: 星期一, 三月 21, 2016 10:59
To: Fred Liu; omnios-discuss
Cc: zfs-disc...@list.zfsonlinux.org<mailto:zfs-disc...@list.zfsonlinux.org>
Subject: Re: [OmniOS-discuss] 4kn or 512e with ashift=12



Hi Fred.

Definitely, the ashift parameter has been around on the illumos for a couple of 
years.

thanks,

Geoff

On 16-03-20 05:21 PM, Fred Liu wrote:
The ashift parameter doesn't apply in illumos if my memory serves me well. It 
was introduced by ZoL.

Thanks.

Fred






On Sun, Mar 20, 2016 at 1:37 PM -0700, "Geoff Nordli" 
<geo...@gnaa.net<mailto:geo...@gnaa.net>> wrote:
Quick, question.

Any performance differences between 4Kn and 512e with ashift=12?

I am thinking there should not be, since they will both write the full
4K block size.

The workload will be virtual machines using a zvol.

thanks,

Geoff
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com<mailto:OmniOS-discuss@lists.omniti.com>
http://lists.omniti.com/mailman/listinfo/omnios-discuss

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com<mailto:OmniOS-discuss@lists.omniti.com>
http://lists.omniti.com/mailman/listinfo/omnios-discuss

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] 4kn or 512e with ashift=12

[Fred Liu]

So, you can “zpool create –o ashift=12” in illumos? I can’t do that in smartos 
at least….

From: Geoff Nordli [mailto:geoff.nor...@gmail.com] On Behalf Of Geoff Nordli
Sent: 星期一, 三月 21, 2016 10:59
To: Fred Liu; omnios-discuss
Cc: zfs-disc...@list.zfsonlinux.org
Subject: Re: [OmniOS-discuss] 4kn or 512e with ashift=12



Hi Fred.

Definitely, the ashift parameter has been around on the illumos for a couple of 
years.

thanks,

Geoff

On 16-03-20 05:21 PM, Fred Liu wrote:
The ashift parameter doesn't apply in illumos if my memory serves me well. It 
was introduced by ZoL.

Thanks.

Fred





On Sun, Mar 20, 2016 at 1:37 PM -0700, "Geoff Nordli" 
<geo...@gnaa.net<mailto:geo...@gnaa.net>> wrote:
Quick, question.

Any performance differences between 4Kn and 512e with ashift=12?

I am thinking there should not be, since they will both write the full
4K block size.

The workload will be virtual machines using a zvol.

thanks,

Geoff
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com<mailto:OmniOS-discuss@lists.omniti.com>
http://lists.omniti.com/mailman/listinfo/omnios-discuss

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] 4kn or 512e with ashift=12

[Fred Liu]

The ashift parameter doesn't apply in illumos if my memory serves me well. It 
was introduced by ZoL.

Thanks.

Fred







On Sun, Mar 20, 2016 at 1:37 PM -0700, "Geoff Nordli" 
> wrote:

Quick, question.

Any performance differences between 4Kn and 512e with ashift=12?

I am thinking there should not be, since they will both write the full
4K block size.

The workload will be virtual machines using a zvol.

thanks,

Geoff
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

[smartos-discuss] RE: kernel zone

[Fred Liu]

From: Fred Liu 
Sent: 星期三, 三月 16, 2016 20:06
To: smartos-discuss@lists.smartos.org
Cc: illumos-developer
Subject: kernel zone

Hi,

Not sure if illumos is designed strictly by backward compatibility. That means 
applications built on older illumos  can still run
on newer illumos. 
For there has been short history of smartos, the older OS images can still run 
well in the current SmartOS release.
But in long-term, will  users be asked to upgrade their images?


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] kernel zone

[Fred Liu]

Hi,

Not sure if illumos is design strictly by backward compatibility. That means 
applications built on older illumos  can still run
on newer illumos.
For there has been short history of smartos, the older OS images can still run 
well in the current SmartOS release.
But in long-term, will the users be asked to upgrade their images?


Thanks.

Fred



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] Imaging LX brand zones

[Fred Liu]

I usually build form source if I want to try a custom image.  The instructions 
are pretty clear.



[Fred]:  The output dir is like following after a successful building:
bash-4.1$ pwd
/home/fliu/smartos-live/output
-bash-4.1$ ls -la
total 158393
drwxr-xr-x  3 fliu fliu 8 Feb 24 19:45 .
drwxr-xr-x 18 fliu fliu26 Feb 26 12:51 ..
-rw-r--r--  1 root root369348 Feb 24 19:43 boot-20160224T102420Z.tgz
-rw-r--r--  1 root root17 Feb 24 19:45 buildstamp
drwxr-xr-x  3 root root 4 Feb 24 19:36 platform-20160224T102420Z
-rw-r--r--  1 root root 161568675 Feb 24 19:45 platform-20160224T102420Z.tgz
lrwxrwxrwx  1 root root25 Feb 24 19:45 platform-latest -> 
platform-20160224T102420Z
lrwxrwxrwx  1 root root29 Feb 24 19:45 platform-latest.tgz -> 
platform-20160224T102420Z.tgz


And definitely, the “boot_archive” can’t be directly used as OS image from 
scratch. I guess we need some scripts and
manifest file to deliver image.

Can you please elaborate your process?

Thanks.

Fred



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] How to mount different zfs volumn to the same lx branded zone

[Fred Liu]

From: Fred Liu [mailto:fred_...@issi.com]
Sent: 星期六, 三月 12, 2016 17:50
To: smartos-discuss@lists.smartos.org; smartos-discuss@lists.smartos.org
Subject: Re: [smartos-discuss] How to mount different zfs volumn to the same lx 
branded zone

It seems hardware pass-through is not applicable in SmartOS from what I know. 
But
there are some indirect methods(NFS/iSCSI) you can try for there is almost no 
network
overhead in LX.


[Fred]: I need to correct my aforementioned typing. Sorry for that! Zones do 
support to import raw and block
devices(including zvol) by using zonecfg. I did test adding  
the smartos usb stick to an OS vm. It works.
   I can make file system(ufs) on it and write some data on it. But 
the bizarre bits are  all the data written in OS
   Vm will vanish if this device is re-imported by global zone 
again. But anyway, passing raw disk to OS vm does occur
  in  heritage from Solaris.



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] How to mount different zfs volumn to the same lx branded zone

[Fred Liu]

It seems hardware pass-through is not applicable in SmartOS from what I know. 
But
there are some indirect methods(NFS/iSCSI) you can try for there is almost no 
network
overhead in LX.

Thanks.

发送自 Outlook Mobile




On Sat, Mar 12, 2016 at 1:02 AM -0800, "Ian Collins" 
> wrote:

On 03/12/16 21:49, 王靖 wrote:
> Thanks for your reply. I try to install NOSQL database aerospike in a > lx 
> branded zone. It seems that aerospike can put data in SSD and > SATA, so I 
> want to have a lx branded zone that have SSD and SATA, in > this way I can 
> store most of the data on SATA while use SSD as a > cache.

You will probably be much better of just using the SSD as a cache for the zones 
pool.

SmartOS is designed to work with a single pool.  Unlike legacy file systems, 
you generally don't have to mess about with drive configurations with ZFS.

--
Ian.

smartos-discuss | Archives 
[https://www.listbox.com/images/feed-icon-10x10.jpg96494be.jpg?uri=aHR0cHM6Ly93d3cubGlzdGJveC5jb20vaW1hZ2VzL2ZlZWQtaWNvbi0xMHgxMC5qcGc]
   | 
Modify Your Subscription   
[https://www.listbox.com/images/listbox-logo-small.png96494be.png?uri=aHR0cHM6Ly93d3cubGlzdGJveC5jb20vaW1hZ2VzL2xpc3Rib3gtbG9nby1zbWFsbC5wbmc]
 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [lustre-discuss] Error on a zpool underlying an OST

[Fred Liu]

You may try recover options(rarely help) from "zpool import" but rebuilding the 
zpool has huge possibilities.

Thanks.

Fred






On Fri, Mar 11, 2016 at 5:19 PM -0800, "Bob Ball" 
> wrote:

Hi, we have Lustre 2.7.58 in place on our OST and MDT/MGS (combined).
Underlying the lustre file system is a raid-z2 zfs pool.

A few days ago, we lost 2 disks at once from the raid-z2.  I replaced
one and a resilver started, that seemed to choke.  So, I put back both
disks with replacements, and the new re-silver shows the following now.

[root@umdist03 ~]# zpool status -v ost-007
   pool: ost-007
  state: DEGRADED
status: One or more devices has experienced an error resulting in data
 corruption.  Applications may be affected.
action: Restore the file in question if possible.  Otherwise restore the
 entire pool from backup.
see: http://zfsonlinux.org/msg/ZFS-8000-8A
   scan: resilvered 972G in 9h25m with 1 errors on Fri Mar 11 19:12:37 2016
config:

 NAME  STATE READ WRITE CKSUM
 ost-007   DEGRADED 0 0 1
   raidz2-0DEGRADED 0 0 4
 replacing-0   DEGRADED 0 0 0
   18280868502819750645UNAVAIL  0 0 0
was /dev/disk/by-path/pci-:0c:00.0-scsi-0:2:20:0-part1/old
   pci-:0c:00.0-scsi-0:2:20:0  ONLINE   0 0 0
 pci-:0c:00.0-scsi-0:2:21:0ONLINE   0 0 0
 pci-:0c:00.0-scsi-0:2:22:0ONLINE   0 0 0
 pci-:0c:00.0-scsi-0:2:23:0ONLINE   0 0 0
 pci-:0c:00.0-scsi-0:2:24:0ONLINE   0 0 0
 pci-:0c:00.0-scsi-0:2:35:0ONLINE   0 0 0
 pci-:0c:00.0-scsi-0:2:36:0ONLINE   1 0 0
 pci-:0c:00.0-scsi-0:2:37:0ONLINE   0 0 0
 pci-:0c:00.0-scsi-0:2:38:0ONLINE   0 0 0
 replacing-9   UNAVAIL  0 0 0
   14369532488179106769UNAVAIL  0 0 0
was /dev/disk/by-path/pci-:0c:00.0-scsi-0:2:39:0-part1/old
   pci-:0c:00.0-scsi-0:2:39:0  ONLINE   0 0 0

errors: Permanent errors have been detected in the following files:

 ost-007/ost0030:<0x2c90f>

what are my options here?  If I don't care about the file, can I
identify it and then just delete it?  Or is my only real option to drain
the pool and rebuild it cleanly?

Thanks for any help/advice.

bob
___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

Re: [smartos-discuss] Imaging LX brand zones

[Fred Liu]

A little bit off-topic, sorry. Is there similar way to create SmartOS(OS) image?

Thanks.

Fred






On Fri, Mar 11, 2016 at 1:11 PM -0800, "Ian Collins" 
> wrote:

On 03/12/16 09:05, Christopher Horrell wrote:
> For SDC/Triton you can create custom images via CloudAPI:
>
> https://docs.joyent.com/public-cloud/instances/infrastructure/images/creating

Thanks, I'm running SDC/Triton so that's a good place to start.

>
> For SmartOS, there isn't a supported process but you can create you
> own Ubuntu, CentOS, Fedora, Alpine or Debian images from scratch for
> SmartOS using one of the following:
>
> https://github.com/joyent/ubuntu-lx-brand-image-builder
> https://github.com/joyent/centos-lx-brand-image-builder
> https://github.com/joyent/fedora-lx-brand-image-builder
> https://github.com/joyent/alpine-lx-brand-image-builder
> https://github.com/joyent/debian-lx-brand-image-builder
>
> We use the above to build the various lx-brand images we make
> available. They are not supported but if you are looking to create
> your own images they should be useful.
>
 
 Yes they are, I've been looking at those for porting client KVM/VmWare
 machines to lx zones.
 
 Cheers,
 
 --
 Ian.
 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [zfs] [developer] Re: [smartos-discuss] an interesting survey -- the zpool with most disks you have ever built

[Fred Liu]

Gotcha!

From: Liam Slusser [mailto:lslus...@gmail.com]
Sent: 星期三, 三月 09, 2016 8:05
To: z...@lists.illumos.org
Cc: smartos-disc...@lists.smartos.org; develo...@lists.open-zfs.org; developer; 
illumos-developer; omnios-discuss; Discussion list for OpenIndiana; 
zfs-disc...@list.zfsonlinux.org; freebsd...@freebsd.org; zfs-de...@freebsd.org
Subject: Re: [zfs] [developer] Re: [smartos-discuss] an interesting survey -- 
the zpool with most disks you have ever built


Hi Fred -

We don't use any cluster software.  Our backup server is just a full copy of 
our data and nothing more.  So in the event of a failure of the master our 
server clients don't automatically fail over or anything nifty like that.  This 
filer isn't customer facing, so in the event of a failure of the master there 
is no customer impact.  We use a slightly modified zrep to handle the 
replication between the two.

thanks,
liam


[Fred]: zpool wiith 280 drives in production is pretty big! I think 2000 drives 
were just in test. It is true that huge pools have lots of operation 
challenges. I have met the similar sluggish issue caused by a
   will-die disk.  Just curious, what is the cluster software 
implemented in 
http://everycity.co.uk/alasdair/2011/05/adjusting-drive-timeouts-with-mdb-on-solaris-or-openindiana/
 ?

Thanks.

Fred
illumos-zfs | Archives 
[https://www.listbox.com/images/feed-icon-10x10.jpg22e4cdf.jpg?uri=aHR0cHM6Ly93d3cubGlzdGJveC5jb20vaW1hZ2VzL2ZlZWQtaWNvbi0xMHgxMC5qcGc]
  | 
Modify Your Subscription

[https://www.listbox.com/images/listbox-logo-small.png22e4cdf.png?uri=aHR0cHM6Ly93d3cubGlzdGJveC5jb20vaW1hZ2VzL2xpc3Rib3gtbG9nby1zbWFsbC5wbmc]





---
openzfs-developer
Archives: https://www.listbox.com/member/archive/274414/=now
RSS Feed: https://www.listbox.com/member/archive/rss/274414/28015062-cce53afa
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=28015062_secret=28015062-f966d51c
Powered by Listbox: http://www.listbox.com

Re: [zfs] [developer] Re: [smartos-discuss] an interesting survey -- the zpool with most disks you have ever built

[Fred Liu]

2016-03-08 4:55 GMT+08:00 Liam Slusser :

> I don't have a 2000 drive array (thats amazing!) but I do have two 280
> drive arrays which are in production.  Here are the generic stats:
>
> server setup:
> OpenIndiana oi_151
> 1 server rack
> Dell r720xd 64g ram with mirrored 250g boot disks
> 5 x LSI 9207-8e dualport SAS pci-e host bus adapters
> Intel 10g fibre ethernet (dual port)
> 2 x SSD for log cache
> 2 x SSD for cache
> 23 x Dell MD1200 with 3T,4T, or 6T NLSAS disks (a mix of Toshiba, Western
> Digital, and Seagate drives - basically whatever Dell sends)
>
> zpool setup:
> 23 x 12-disk raidz2 glued together.  276 total disks.  Basically each new
> 12 disk MD1200 is a new raidz2 added to the pool.
>
> Total size: ~797T
>
> We have an identical server which we replicate changes via zfs snapshots
> every few minutes.  The whole setup as been up and running for a few years
> now, no issues.  As we run low on space we purchase two additional MD1200
> shelfs (one for each system) and add the new raidz2 into pool on-the-fly.
>
> The only real issues we've had is sometimes a disk fails in such a way
> (think Monty Python and the holy grail i'm not dead yet) where the disk
> hasn't failed but is timing out and slows the whole array to a standstill
> until we can manual find and remove the disk.  Other problems are once a
> disk has been replaced sometimes the resilver process can take
> an eternity.  We have also found the snapshot replication process can
> interfere with the resilver process - resilver gets stuck at 99% and never
> ends - so we end up stopping or only doing one replication a day until the
> resilver process is done.
>
> The last helpful hint I have was lowering all the drive timeouts, see
> http://everycity.co.uk/alasdair/2011/05/adjusting-drive-timeouts-with-mdb-on-solaris-or-openindiana/
> for info.
>
> [Fred]: zpool wiith 280 drives in production is pretty big! I think 2000
> drives were just in test. It is true that huge pools have lots of operation
> challenges. I have met the similar sluggish issue caused by a
>
   will-die disk.  Just curious, what is the cluster software
implemented in
http://everycity.co.uk/alasdair/2011/05/adjusting-drive-timeouts-with-mdb-on-solaris-or-openindiana/
 ?

Thanks.

Fred

>
>
>
>>>
>>>
>>
> *illumos-zfs* | Archives
> 
>  |
> Modify
> 
> Your Subscription 
>



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [zfs] [developer] Re: [smartos-discuss] an interesting survey -- the zpool with most disks you have ever built

[Fred Liu]

2016-03-08 4:55 GMT+08:00 Liam Slusser :

> I don't have a 2000 drive array (thats amazing!) but I do have two 280
> drive arrays which are in production.  Here are the generic stats:
>
> server setup:
> OpenIndiana oi_151
> 1 server rack
> Dell r720xd 64g ram with mirrored 250g boot disks
> 5 x LSI 9207-8e dualport SAS pci-e host bus adapters
> Intel 10g fibre ethernet (dual port)
> 2 x SSD for log cache
> 2 x SSD for cache
> 23 x Dell MD1200 with 3T,4T, or 6T NLSAS disks (a mix of Toshiba, Western
> Digital, and Seagate drives - basically whatever Dell sends)
>
> zpool setup:
> 23 x 12-disk raidz2 glued together.  276 total disks.  Basically each new
> 12 disk MD1200 is a new raidz2 added to the pool.
>
> Total size: ~797T
>
> We have an identical server which we replicate changes via zfs snapshots
> every few minutes.  The whole setup as been up and running for a few years
> now, no issues.  As we run low on space we purchase two additional MD1200
> shelfs (one for each system) and add the new raidz2 into pool on-the-fly.
>
> The only real issues we've had is sometimes a disk fails in such a way
> (think Monty Python and the holy grail i'm not dead yet) where the disk
> hasn't failed but is timing out and slows the whole array to a standstill
> until we can manual find and remove the disk.  Other problems are once a
> disk has been replaced sometimes the resilver process can take
> an eternity.  We have also found the snapshot replication process can
> interfere with the resilver process - resilver gets stuck at 99% and never
> ends - so we end up stopping or only doing one replication a day until the
> resilver process is done.
>
> The last helpful hint I have was lowering all the drive timeouts, see
> http://everycity.co.uk/alasdair/2011/05/adjusting-drive-timeouts-with-mdb-on-solaris-or-openindiana/
> for info.
>
> [Fred]: zpool wiith 280 drives in production is pretty big! I think 2000
> drives were just in test. It is true that huge pools have lots of operation
> challenges. I have met the similar sluggish issue caused by a
>
   will-die disk.  Just curious, what is the cluster software
implemented in
http://everycity.co.uk/alasdair/2011/05/adjusting-drive-timeouts-with-mdb-on-solaris-or-openindiana/
 ?

Thanks.

Fred

>
>
>
>>>
>>>
>>
> *illumos-zfs* | Archives
> 
>  |
> Modify
> 
> Your Subscription 
>



---
openzfs-developer
Archives: https://www.listbox.com/member/archive/274414/=now
RSS Feed: https://www.listbox.com/member/archive/rss/274414/28015062-cce53afa
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=28015062_secret=28015062-f966d51c
Powered by Listbox: http://www.listbox.com